The problems you know
Eng is a bottleneck
Every landing page request becomes a ticket. By the time it ships, the campaign has moved on. You need to control the page yourself.
CMS templates feel canned
WordPress and HubSpot landing pages all look the same. Your campaigns deserve specific design, not a global template.
Tracking always breaks
Hand-built pages lack proper UTM handling, conversion tracking, structured data. Every campaign reinvents the wheel.
Tests take weeks
A/B test variants need eng to deploy. By the time the variant ships, the test window is gone.
How InBuild solves them
From prompt to live page, no ticket required
Describe the campaign. Watch AI generate a full landing page — hero, social proof, features, FAQ, CTA — stage by stage. Edit in the visual editor, publish, share the link.
Variants in a few clicks
Duplicate a page, regenerate just the hero with a different angle, publish at `/p/[id]/v2`. A/B test with your existing tool (PostHog, Optimizely).
SEO basics out of the box
Every page emits metadata and OG images (no structured data / JSON-LD — InBuild doesn't generate that for your project). Form submissions hit your Forms dashboard with the page route, IP, and user agent — no UTM or campaign attribution is captured, so wire your own if you need it.
Export when you need custom
When you need to do something AI doesn't generate, export the Next.js code and hand it to engineering. No vendor lock-in.
Frequently asked questions
Can I use this without engineering involved?
Yes — that's the design center. Marketing builds in InBuild; eng gets involved when the campaign needs custom backend (gated content, complex tracking, multi-step flows that exceed our form builder).
How does this integrate with my marketing stack?
Form submissions land in your Forms dashboard with CSV export → import to HubSpot/Mailchimp/Salesforce. There's no Design-panel field for dropping in a GA/Plausible/PostHog snippet or capturing UTMs — after you export, add the analytics script and any UTM handling directly to app/layout.tsx in the codebase.
What about brand consistency across campaigns?
Set theme colors and fonts once at the project level — every page in that project inherits the brand. For multi-brand agencies, one InBuild project per brand.