A new campaign, and a ticket in the developer queue
Marketing wants a landing page for a new service, or an event, or a paid campaign starting Monday. The website was built by a developer who is now busy with other work, or by an agency that charges for each change. So a ticket goes in, the page arrives late, the ad launches pointing at the homepage, and the page that finally appears needs three rounds of fixes.
Some teams try a separate landing page tool. Now there are two sets of branding, forms that go to a different place from the main site and tracking set up twice.
The irony is that most landing pages are variations on the same few sections. A headline, a picture, some reasons, some proof, a form. The developer is not being asked to solve a new problem each time. They are being asked to copy and adjust the last page, which is exactly the work a well-built CMS should let a marketer do.
Why every page still needs a developer
The site was built as a set of individual pages, not as a set of reusable parts. Any new layout means new code.
- Page templates are rigid, so anything slightly different needs a developer.
- Forms are hand-built per page, each with its own connection to the CRM.
- Tracking tags are added page by page and often forgotten.
- Marketers are nervous of the page builder because they have broken the layout before.
- Separate landing page tools sit outside the main site, splitting data and design.
What waiting costs
Campaigns launch late or send paid traffic to generic pages that do not match the ad. Small tests never happen because each one needs a ticket. Developer time goes on low-value page building instead of things only a developer can do.
| Approach | Speed for marketers | Risk |
|---|---|---|
| Developer builds every page | Slow | Low, but campaigns wait |
| Free-form page builder | Fast | Broken layouts, slow pages, missing tracking |
| Separate landing page tool | Fast | Split branding, forms and data |
| Approved block library in your CMS | Fast | Low, because blocks are pre-tested |
How we set marketing free
- We audit your existing pages and list the sections you actually use: hero, benefits, proof, pricing table, FAQ, form, call to action.
- We build each section as a reusable block in your CMS, such as WordPress with Gutenberg or ACF blocks, Webflow components, or a headless CMS like Sanity or Strapi feeding your front end.
- Each block has limited, sensible options (image, heading, text, colour variant) so the page stays on brand whatever the marketer chooses.
- One form block connects to your CRM with hidden fields for source and campaign, so every page's leads arrive correctly tagged.
- Tracking and consent handling are built into the page template, so new pages are tracked automatically.
- We check blocks for speed and mobile layout once, so every page built from them inherits the result.
- We write a short guide and train the team on assembling and publishing a page.
If you already use a separate landing page tool and like it, we can instead make it behave like part of your site: same fonts and colours, forms posting to the same CRM with the same fields, and the same consent and tracking setup. Which route is better depends on how many pages you make and who makes them.
How campaigns run after this
A marketer duplicates a starting template, swaps the headline, picks the blocks, sets the form's campaign tag and publishes. The developer gets involved when a genuinely new component is needed, and that new block then joins the library for everyone.
Leads from every landing page land in the CRM with their source, and testing a different headline becomes a small job rather than a ticket.
Sounds familiar?
- Every landing page needs a developer or agency ticket.
- Paid campaigns have launched pointing at the wrong page because the right one was not ready.
- Forms on different pages send leads to different places.
- Someone has broken the layout in the page builder and nobody wants to touch it now.
- You run a separate landing page tool alongside your main site.