The marketing site waits behind the product roadmap
The site lives in the product codebase, so a campaign page is a ticket in an engineering sprint. The launch window closes while the request waits its turn, and marketing learns to stop asking.
Astro buildsAstro Web
Astro Web
Development Agency
A marketing site that loads fast on every page, sits in your own repository next to the product, and costs almost nothing to host.
Marketing publishes through a connected CMS, engineering keeps the code, and the whole thing runs on the same design system we build for Webflow Enterprise clients.
Get in touch
Before and After
What Changes When the Site Leaves the Product Sprint
The ProblemStandard Agency
Nobody in-house understands the stack
The site was built by someone who left, in a framework the team never chose. Every change carries the risk of breaking something, so the site stops changing and stops reflecting what the company sells.
Every page carries script it never uses
A site built as an application ships its whole runtime to every visitor. Pages load slowly on the phone a prospect is holding, and the paid campaign pays for every second of it.
The Solution
The Legency Approach
The Legency ApproachMarketing publishes, engineering keeps the code
Content lives in a CMS your team already knows how to use. An editor fills in fields, picks sections from an approved set, previews the page and publishes. No developer in the loop for a campaign page.
Every page renders as plain HTML
The site ships finished HTML and adds script only where a page needs it. Our own site measures 97 for desktop performance, with the largest element painted in 1.3 seconds and 74 kB of script transferred.
The company owns the site outright
Full source in your repository, hosted on infrastructure you control, with every change recorded and reversible. A new developer, an AI coding assistant or another agency can pick it up from the documentation.
What the Build Carries
What an Astro Build Buys Marketing
One Design System Across Astro and Webflow
We build Astro sites from the same shared design system as our Webflow Enterprise work: reusable sections, one spacing and typography scale, the same responsive rules. A page looks and behaves the same whichever platform it ships on, so the brand holds across the estate.
Hosting Without Per-Seat Platform Fees
A static site serves from an edge network with no bandwidth ceiling and no monthly platform tier to defend at budget review. The accounts the site depends on, its CMS, forms and analytics, are listed with their costs in the proposal, so nothing surprises finance later.
A Handover Written for Whoever Comes Next
Every build ships with context files that describe how the site is put together, the commands that build and deploy it, and how to restore the previous release. A new hire, or the AI assistant your team already uses, reads those before touching anything.
When Astro Fits
Four Sites That Belong on Astro
We are a Webflow Enterprise partner and we build on Astro when the site's operating needs point there. These are the four cases where they do.
Content & publishing
A content site that has to be fast everywhere
Resource libraries, documentation, editorial sites and any estate where paid campaigns land on content pages. Plain HTML on every page means the prospect on a phone in a lift sees the page before the lift stops.
Marketing & product
A marketing site beside a software product
When engineering already runs a repository, a marketing site that lives next to it gets the same reviews, previews and release process. Marketing still publishes through the CMS, and engineering never becomes the bottleneck for a campaign page.
Structured content
A large structured catalogue
Thousands of product, location or programme pages generated from a data source. A framework build has no collection ceiling, so the catalogue is modelled once and grows without a migration later.
Ownership & continuity
A company that wants to own the code
Procurement, security or an engineering culture that requires the site in the company's own repository, on infrastructure the company controls. The site is yours in full from the first commit.
Honest Limits
Where Astro Is the Wrong Answer
We build on Webflow more often than on Astro, and we say which one fits on the first call. Hearing it then is cheaper than discovering it mid-build.
A team that wants to edit visually every day
If marketing wants to move sections, restyle a page and publish without a preview step, Webflow's editor is the better tool. An Astro site edits through a CMS, and the CMS decides what the editing experience feels like.
Nobody to own the dependencies
A framework site needs someone responsible for its packages, integrations and hosting account. If that person does not exist and a support agreement is off the table, a managed platform is the safer home.
A site that is really an application
Account areas, complex permissions and heavy transactional flows belong in the product, whichever framework builds the marketing site beside it. We scope the boundary between the two before the build starts.
Case Study
The same system that carries Blueflame carries our Astro work.
Blueflame’s marketing team publishes on a component library that has carried the company through a funding round, an acquisition and a rebrand. Our Astro builds use the same design system and the same handover discipline, on a code base the client owns.
View Case Study
Start With Who Publishes
Talk to the Person Who Will Build It
The first call is with the person who will structure the build, because the questions that decide an Astro site are operational: who adds the next article, who needs a campaign page by Thursday, and who looks after the code once it is live.
- Who on your team publishes, and which CMS gives them previews and approvals
- Where the site lives, who owns the repository and who deploys
- Whether Astro is the right platform for you at all, answered on the first call
Common QuestionsFrequently Asked
Frequently Asked
Questions
Yes, for a content-heavy site that has to load fast on every page, or one that belongs in a code repository beside the product. Astro renders pages as plain HTML by default and adds script only where a page needs it. Our own site runs on it and measures 97 for desktop performance.
Yes, through a connected CMS. An editor fills in fields, chooses sections from an approved set, previews the page and publishes, and the site rebuilds on its own. Which CMS we connect depends on who is publishing and how often, which is why we ask before we recommend a stack.
Webflow gives marketing the best native editor there is, and for a team publishing several times a week with no developer nearby it is often the right answer. Astro gives the company full ownership of the code, faster pages by default and lower running costs, with editing through a CMS we connect. We build on both and say which fits on the first call.
The pages themselves serve from an edge network with no bandwidth charge and no platform tier. The running cost is the services around the site: the CMS, forms, analytics and any search index. Each one is named with its price in the proposal.
Yes. We audit what exists, rebuild the templates as reusable sections, and map every URL to its new home with redirects in place before launch. The old site stays live until the new one is proven, and search rankings are monitored through the switch.
You keep everything: the repository, the documentation and the design system. We can run the site for you under a support agreement, or hand it to your team or another developer with the build notes and deployment steps written down.