Problem · Startups
Our engineers refuse to touch the marketing site and marketing cannot ship without them.
Either the marketing site lives in the product repo and every landing page is a sprint ticket that loses to a feature, or it lives on a page builder the engineers will not go near and it loads in four seconds with the wrong schema. Both are the same problem: nobody decided who owns the site or what it runs on. Decide both, and the fight ends.
How people search thiswho should own the marketing website engineering or marketing · marketing site separate from product repo · startup marketing website stack · nextjs marketing site for startup · engineers wont update marketing website
Every ISOVERTIC build ships on Next.js, TypeScript, and Vercel, server rendered, with content as typed data your engineers can read and marketing can edit. Included with a 12 month term or $15,000 up front month to month. Repo is yours on day one. Pricing is published.
Separate the site from the product
The marketing site and the product are different systems with different release cadences. Put the site in its own repository on its own deployment, so a landing page ships in an afternoon without touching the product pipeline. Engineering reviews the initial build and the deploy setup once. After that, marketing ships copy and pages without a ticket, and engineering never sees a marketing PR again.
A stack engineering will not rip out
Next.js with TypeScript, server rendered, on Vercel, with content in typed files or Postgres. It is what your first engineering hire already knows, it renders fully for crawlers and AI engines, and it has no plugin layer to rot. Content lives in typed data files: a services file, an articles folder, a schema builder. Marketing edits copy; the type checker catches the mistakes; the build fails before the typo ships. That is the stack every build we ship uses, and the reason engineers approve it in one review.
Who owns what, written down
Engineering owns the deploy pipeline, the domain, and the initial review. Marketing owns every page, every word, and the publishing cadence. The growth partner, if you have one, builds inside that split and hands the repo back with the runbook for adding a page. Request any page without JavaScript and read the copy; that is the acceptance test, and it is the one most page builder sites fail.
Questions on this problem
Copy lives in typed content files and markdown, not in components. A marketer edits a sentence, the preview shows it, the type check passes, it ships. Most learn it in a day.
Fine when there are ten editors. For a startup with two, typed files are faster, cheaper, and version controlled for free. We add a database when the content outgrows the files.
Yes. They review the build and the deploy once. Our founder writes the build briefs our coding agents execute and speaks their language.
George Stoff, Founder and Lead Engineer
Thirty years building software, brands, and demand. On every account.