We rebuilt the iGsuite website from scratch with AI at every stage: Claude Code for architecture, Lovable for design prototyping, and Next.js with Sanity CMS underneath. AI delivered about 80% of the result in days, but matching our brand, fixing mobile and wiring the CMS properly took five weeks. This is the honest breakdown of what each tool did, where it fell short, and what we'd tell any team planning an AI-assisted build in 2026.
What Was the Brief, and Why Wasn't It Done in a Day?
The brief was simple: migrate off WordPress, go live on something modern. Done.
It was not done.
Our co-founder and senior software engineer Valentina led the rebuild from architecture to DNS cutover, using Claude Code, Lovable, ChatGPT and Midjourney. Not as a gimmick, but as actual build infrastructure. The result is the site you see at igsuite.com today: dark, cinematic, glassmorphism, premium. The kind of landing page where you feel in the first three seconds that the people behind it know iGaming.
We're sharing this because a credible web presence is one of the first real challenges any new iGaming business faces, as we also note in our launch checklist, and the way you build one has fundamentally changed. If you're a startup operator, a new platform, or a team about to leave a legacy CMS, this is the account we wish we'd had before we started.
Why Premium B2B and Not Generic SaaS?
Before a single line of code, the brief was specific. Dark, cinematic. Glassmorphism - frosted glass navigation, cards lit from inside. Electric blue as the primary accent, warm gold #e8a33d for stars and highlights, brand red used almost never. IBM Plex Sans for headlines, IBM Plex Mono for the eyebrow labels. Restrained - no disco colors, no neon overload. The kind of site that communicates immediately: this was built by operators for operators.
That vision took five weeks to execute, not five days. And the gap between the two is the most instructive part of the story.
How the AI Stack Was Actually Used?
- Claude Code handled the architecture. Next.js + Sanity CMS. Blog schema, SEO scaffolding, deploy pipeline - all of it built in the first few days. The bones were solid fast. Claude Code is genuinely strong when the brief is precise: ‘build a Sanity webhook that triggers a redeploy on publish’ produces clean results. ‘Make it feel more premium’ does not.
- Lovable handled design prototyping. The About page - flip cards, ambient gradients, the full dark cinematic treatment - was built properly in Lovable first, then exported and ported into Next.js. The tool gets you 80% of a polished visual in minutes. Matching the remaining 20% pixel-for-pixel in production took the rest of the project.
- ChatGPT and Midjourney were tried and dropped. Both were tested for ambient background generation. Both kept producing full hero compositions with text baked in. Neither matched the brand kit cleanly. Sometimes the right answer is to recognize when a tool isn't the right fit for a specific task and move on.
What No AI Tool Could Do: Learn Your Brand
This is the lesson at the center of everything. No AI tool — not one — understood the iGsuite brand on the first prompt, or the tenth. The navigation went back and forth ten times before settling. The glow on cards had to be specified precisely: top edge, not corner. The rule that only one keyword per heading gets the blue accent - that came from iteration, not instruction. The exact blur radius that reads as 'frosted glass' rather than 'blurry rectangle' - same.
Every font, every color decision, every nuance was manually worked through and then had to be repeated until it landed. AI tools compress timelines. They do not replace taste, and they do not absorb your brand identity from a single brief.
The formula, honestly: AI gives you 80% in 5% of the time. The remaining 20% takes the other 95%.
What Are the Key Takeaways for an AI-Assisted Build?
- Precision beats volume. Vague briefs produce generic output. Name the component, the exact colors and the hover behavior, and map each task to the file it lives in.
- Prototype visually before you build. Use Lovable or a similar tool to reach 80% of the visual target first. Porting a finished design is faster than designing directly in code.
- "Connected" is not "controls." Our Sanity CMS was wired before the site was hardcoded. The integration existed but did nothing. Verify the CMS actually drives your live content.
- Mobile is its own project. A site that looks cinematic on a monitor can lag and flash white on a phone. Since mobile now drives most online gambling revenue, budget dedicated time for it.
- Run an AI search audit of your brand. Ask the major AI tools what they recommend in your category. If you're not in the answer, you have a plan to build.
What Comes Next After Going Live?
The site is live. The glass nav scrolls smooth, the forms work, and the blog is running real content. If you're at this stage yourself, congratulations: the hard part is done. The next chapter is visibility, with SEO to build organic authority and GEO (Generative Engine Optimization) to make sure your brand shows up when AI tools answer the questions your future customers are already asking. That is the project we've already started.
Frequently Asked Questions
- Can AI build a production website on its own? Not on its own. AI delivered about 80% of ours in days, but brand fidelity, mobile performance and CMS wiring needed human iteration.
- Which AI tool is best for design and which for code? In our build, Lovable was best for visual prototyping and Claude Code for architecture and precise engineering tasks.
- How long does an AI-assisted rebuild really take? Ours took five weeks end to end. The first 80% took days, and the last 20% took most of the time.
Go see it at igsuite.com.
Let's Scale Together🚀
We're building the future of the iGaming ecosystem, and we want you in the loop. Follow us on LinkedIn for a behind-the-scenes look at our newest features.