> Hourly Astro advisory: architecture, performance, code review, multi-market structure and CMS integration, from a senior engineer who ships Astro sites daily.

Canonical: https://augustynglowacki.com/services/astro-consultancy

# Astro consultancy

Which components need to be islands, which routes need a server, and whether the content lives in collections or a CMS. I settle these before the build, or trace a slow Astro page back to them. Send the slow page, planned build or pull request, and I recommend what to change first.

[Send the question](#lead-form)

## Astro problems that pass the build

An Astro site can build cleanly and still do work no page needed. I trace each of these back to a line in the code.

### An island that never needed to be one

A `client:*` directive on a component with no interactive state sends JavaScript to every page that renders it. I name the directives to remove.

### An adapter that behaves differently at your host

I check how static output and the server adapter behave on your host, then recommend an output mode for each route.

### A content reference that points at nothing

Astro logs a dangling `reference()` and still exits zero ([astro#13268](https://github.com/withastro/astro/issues/13268)). I recommend a stricter schema and a check that fails the build.

## Before booking an Astro review

### What does this cover?

Architecture before a build or a migration: rendering mode, adapter, content collections or a CMS, which components are islands. Performance, each Core Web Vitals metric traced to its cause. Code review on pull requests, boundaries and schemas. Multi-market structure, and the AGENTS.md that lets a new developer or a coding agent ship a first change.

### Do you plan the migration, or run it?

I plan it: the order of operations, what moves at each step, and what breaks out of order. Advisory ends at the change list. If you want me to run the migration, I write the changes up as a roadmap of tasks, each estimated in hours, and carry them out as you approve them, at 75 USD an hour excl. VAT.

### Can you set up Claude Code for our Astro codebase?

Yes. I write the AGENTS.md, project rules and checks a coding agent needs to ship a first change without breaking the build. I test them on a real task in your repository before handing them over.

### How is the time scoped?

I read the code first, then reply with a fixed number of hours at 100 USD an hour excl. VAT, with a 300 USD minimum. A pull request or a single islands question is usually a few hours, an architecture or multi-market review a day or two. Nothing starts before you agree the hours.

## When the Astro question turns out to be a content question

A question about an Astro page can start with the way its content is structured. I review the content model with the templates that use it, including the Sanity or Storyblok integration when that is part of the problem.

### Sanity CMS consultancy

The content model, Studio and GROQ queries behind a Sanity site, reviewed before the schema locks in or when editors start working around it.

[See what's included](/services/sanity-consultancy)

### Storyblok CMS consultancy

The component library, Visual Editor and frontend behind a Storyblok site, reviewed before editors build pages or when preview stops matching the site.

[See what's included](/services/storyblok-consultancy)

### Next.js consultancy

Stale pages, slow routes and caching rules in a Next.js app, traced to the code that causes them.

[See what's included](/services/nextjs-consultancy)

## How an Astro review runs

The result is a change list your team applies without me on a call.

### Send the repo and the question

Read access and a sentence on what is bothering you.

### I read the build first

The islands, adapter config, collections or CMS queries your question touches, then a fixed number of hours at 100 USD an hour excl. VAT, with a 300 USD minimum.

### You get a change list

In the order to fix it, each item naming the file it touches.

## Start the Astro review

### Send the Astro question

Share the repository and the rendering, CMS or performance problem you want reviewed.

### Agree the review

You get the scope and the hours in writing before anything starts.

### Get a change list

The cause, and the changes in the order to make them, written for your team to apply.

[Send your brief](/contact#lead-form)
