WeInc

Inspiration

What it does

Inspiration

Most people who need a website are not designers and do not want to become one. They open a website builder, meet a blank canvas or a grid of templates that look nothing like their business, and stall. We wanted to remove the canvas entirely: you describe your business in a sentence, and a finished site is waiting for you.

What it does

WeInc turns a sentence into a working website. Describe your business and the AI builds a complete multi-page site, writes the copy, picks the images and lays out the design in about 15 seconds.

Everything is editable two ways. You can click straight onto the page and change text, colours, spacing and images in place. Or you can tell the AI what to change in plain English and it edits the code for you.

When you are happy, publish to a free subdomain or connect your own custom domain. WeInc also builds full web apps, not just brochure sites, and agencies can run the whole platform white-label under their own brand for their clients.

Free to start. Paid plans from $20 a month.

How we built it

Next.js App Router with Tailwind on the front end. Generated projects run inside WebContainers, so a real Node toolchain boots in the browser tab and the preview you see is the actual app running, not a mock. Monaco provides the code editor.

The AI layer streams structured file operations rather than prose, which a parser turns into writes against the in-browser filesystem. Supabase handles auth, Postgres with row level security, realtime and storage. Stripe covers subscriptions, and Stripe Connect powers the white-label billing for agencies.

Challenges we ran into

Editing an existing site is much harder than generating one. A model asked to change a headline will happily rewrite a whole file and quietly destroy work. Fixing that meant tighter file targeting, componentisation, and verifying that what the model claims it changed is what actually landed on disk.

Browser-side builds were the other wall. WebContainers need cross-origin isolation headers, which break OAuth if applied globally, so those headers are scoped to the builder routes only. Phones cannot run WebContainers at all, which meant building a server-side build path so mobile users can still publish.

What we learned

Speed to a first result changes behaviour more than any feature. Once a real site appears in 15 seconds, people start editing instead of abandoning. And reliability of edits matters more than raw generation quality, because the first build is a demo while the fifth edit is the product.

What's next for WeInc

Deeper visual editing that approaches design-tool control, richer ecommerce, and expanding the white-label platform so agencies can run their entire client base on it.

How I built it

Challenges I ran into

Accomplishments that I'm proud of

What I learned

What's next for WeInc

Built With

• anthropic
• next.js
• react
• supabase
• tailwind
• typescript