Astro consulting: even when the answer is no.
Independent Astro consulting for teams with their own developers: does Astro fit the plan, is the codebase healthy, how should the content model look? Four modules, bookable individually.
Open-ended by design
We also build in Webflow and we build custom software. A recommendation against Astro is a regular outcome.
Written, not verbal
Every module ends with a document: recommendation, reasoning, alternatives, risks and the effort attached.
Short and time-boxed
Modules run days to a few weeks and end with a decision.
Our own products, live in the browser.
Screenshots from Mini Marvin, our own progressive web app running in the browser.
Swipe baby names instead of scrolling
Mini Marvin is our progressive web app for finding baby names: swipe through 10,000+ first names right in the browser, no app store needed.
Four modules, bookable individually.
-
Framework decision review
The independent answer to whether Astro is the right foundation for this project. The recommendation can read "no Astro".
Astro vs. Next.jsMore on this
We look at what the site has to do, how many genuine page types exist, where the content comes from and who owns operations. The result is a written recommendation with reasoning, at least one named alternative and an effort range.
-
Astro architecture review
How page types, content collections, the CMS boundary and the rendering strategy have to be cut before any code exists.
Astro CMS & content collectionsMore on this
The most expensive mistake in an Astro project is rarely the code, it is the content model. You get a page-type matrix, a schema draft and a rendering decision per route. What stays as Markdown in the repository and what belongs in a headless CMS is part of it.
-
Astro code review
A read through an existing codebase: hydration, rendering strategy, schema discipline, images, dependencies and build.
Performance optimizationMore on this
Every finding gets two values, impact and effort. From those come four baskets: fix now, fix next sprint, plan as a rebuild, and leave alone deliberately. You receive the list with references and a walkthrough with your team.
-
Team enablement
Your in-house team becomes productive in Astro: agreed conventions, two workshop days and accompanied weeks of pairing and reviews.
Astro web developmentMore on this
The default is no client directive, and every single one needs a documented reason. The conventions land as a document in your repository. Teams coming from React hydrate too much at first, and that reflex is what the accompanied weeks retrain.
Facing a decision that gets expensive?
Describe in three sentences where you stand. You get an assessment of which module fits and whether one is needed at all.
When consulting is the right format.
The filter we apply in the first call. The right-hand column costs us work regularly.
Consulting fits when …
A decision is coming that will be hard to reverse later.
- You are facing a decision that gets expensive later: framework, content model, CMS boundary, rendering strategy.
- You have an in-house development team that will do the building and needs a defensible basis.
- You have to assess a proposal whose effort and architecture nobody in-house can judge.
- You inherited someone else's Astro codebase and want to know what is waiting inside it.
Something else fits better when …
Then we say so in the first call and point you elsewhere.
- You want it built. Then the route runs straight to Astro web development or migration to Astro.
- The decision has already been made internally and a review is meant to endorse it.
- The problem sits outside the framework, in ownership and deadlines. Then IT project management fits.
- Neither budget nor capacity is planned for the follow-up work. A report nobody acts on helps nobody.
How a consulting module runs.
First call
30 to 45 minutes on the project, its state and the bottleneck. Then we say which module fits.
Scope and proposal
Module, scope, duration, the access we need and what you hold at the end.
Material and access
Read access to the repository, existing documentation, field and analytics data.
Review
We read, measure and calculate, and put our questions to you in one batch.
Report and walkthrough
A document, then a round with the people who decide. The module ends there.
Frequently asked questions about Astro consulting.
Can you recommend against Astro?
Yes, and it is a regular outcome. We also build in Webflow and we build custom software, so our revenue does not depend on the answer. What you pay for is the review, and the finding comes out either way.
How long does a module take?
Framework decision review three to five working days across one or two weeks. Architecture review one to two weeks from the workshop day. Code review three to eight working days. All four modules in sequence take four to eight weeks of calendar time.
What does consulting cost, and why is there no price here?
The shape varies too much for one number. Effort follows the number of modules, the size and age of the codebase, the number of page types and languages, and on-site workshops. What a build costs is on Astro development cost.
What does an Astro code review find that our team does not see?
Usually what any grown project accumulates: client:load where client:visible would have done, routes rendering at request time that could be prerendered, a schema that went soft over the months, images in the public directory bypassing the built-in optimisation.
Do you need access to our production systems?
No. Read access to the repository is enough, plus build logs, the configuration without secrets, and field data from your analytics environment. Production credentials, editor accounts and customer data stay with you.
Do you check whether our content model works for AI agents?
Yes. A schema validated through Zod can be filled by an agent too, because it can only write existing fields in valid formats and every change lands as a commit. Our own WhatsApp AI agent is the evidence for that experience.
Further reading in the Astro cluster.
The pages the modules lean on most often:
An independent answer before it gets expensive.
Describe the project, its state and the decision ahead. You also hear when no module is needed. Usually within 24 hours.
Request Astro consulting.
A short description is enough: decision, architecture, an existing codebase or team enablement.
We usually reply within 24 hours.
Remote and on site in Germany, Austria and Switzerland. International projects on request.