services · 17 offers · 5 groups
Faster sites.
Cleaner stacks.
Rankings that survive the move.
Jamstack development on Next.js, Astro and Nuxt, with a headless CMS your editors will use, migrations that keep every ranking, and technical SEO that holds up in AI search.
17 services in five groups: build it, move it, grow it, name it, run it. Pick the problem you have. The stack follows from your timeline, your editors, and your performance budget.
why jamstack now
The plugin tax, the PHP surface and the Core Web Vitals gap are one problem.
Most sites I audit are paying a plugin tax: twenty to forty extensions, each loading its own scripts and styles on every page, each a dependency somebody has to patch. The site gets slower every quarter and nobody made a decision for it to.
The same architecture puts a PHP runtime in every request path. When PHP2Shell landed, governments pulled sites offline on 21 October because PHP sat between every visitor and every page, while static and headless builds stayed up. Fewer moving parts in the request path is a security decision as much as a speed one.
Core Web Vitals are a ranking signal measured on real visits, and the pass rate is the gap between a page pre-rendered to a CDN and a page assembled on a server for every visit. Next.js, Astro and Nuxt pass the budget by default; the work is keeping it that way as the site grows.
None of this works if editors lose their editor. A headless CMS, Sanity, Payload, Storyblok or Contentful, gives the content team drafts, previews and a visual editor while the public site ships as static HTML. The stack changes; the publishing workflow gets better, not harder.
where i help
Three places the work lands.
-
Jamstack development: Next.js, Astro and Nuxt, with headless CMS development
Next.js development when the product needs app behaviour and server rendering. Astro development when content and speed lead. Nuxt when your team writes Vue. Behind each, headless CMS development on Sanity, Payload, Storyblok or Contentful, so editors get drafts, previews and a real editor while the public site ships as static HTML. Technical SEO and a Core Web Vitals budget go in with the first commit.
-
Migration from PHP and legacy CMS to Jamstack, rankings intact
Drupal, Joomla, TYPO3 and other PHP estates re-platformed to Next.js or Astro as an SEO project, not a rebuild. The redirect map comes from Search Console and Ahrefs traffic, not a sitemap export. Titles, descriptions, canonicals, hreflang and schema are carried across byte-identical and diffed before launch. Cutover runs with monitoring on, and the new sitemap goes in the same day.
-
Growth: technical SEO, Core Web Vitals and AI-search citability
Audits and fixes across crawl, index, schema, hreflang and Core Web Vitals, measured on CrUX field data rather than a lab score. Answer-first copy and entity markup so AI Overviews, ChatGPT and Perplexity cite you. Programmatic SEO behind quality gates when the opportunity is thousands of pages, on the playbook that runs HostList.io.
Build
New sites and platforms, designed and coded from scratch. Technical SEO and a speed budget go in with the first commit.
Discuss your project- Jamstack Development Next.js, Astro and Nuxt builds served from a CDN, with a headless CMS your editors will use. No PHP in the request path, SEO lint and a Core Web Vitals budget on every build, code yours at launch.
- MVP Development A product idea taken from a one-line brief to a live app with sign-up, payments and analytics, on Next.js or Astro, Supabase and Stripe. Every MVP ships with WebMCP tools so AI agents can use it.
- Web Design and Development Custom-coded sites with original design across Next.js, Astro, Nuxt, and headless CMS platforms. Every build ships with technical SEO foundations and a Core Web Vitals budget.
- Website Redesign An existing site rebuilt around the problem it cannot solve, with every URL that earns traffic mapped to a 301 before anything is designed, so the rankings move with it.
- Headless CMS Development CMS selection, content modelling and studio setup on Sanity, Payload, Storyblok, Contentful or Strapi, wired to a Next.js or Astro front-end with previews editors trust.
- Directory Website Development Programmatic-SEO directory and listing platforms on Next.js plus Supabase. Built by the operator behind HostList.io, 30,000+ web hosting companies ranked by data since 2024.
- Portfolio Web Design Portfolio sites built as lead engines, not galleries. The case study is this site: 3,100+ URLs in 8 languages, publishing on autopilot from a custom admin.
- Enterprise DAM Consulting Independent help choosing a digital asset management platform, setting up its metadata and taxonomy, and migrating every asset into it, with no vendor commissions.
Move
Re-platforming without losing rankings. Redirect maps come from real traffic data. Metadata is carried across byte for byte. And the DNS cutover is one nobody notices.
Discuss your project- Site Migration Complex CMS migrations, headless re-platforming, and host moves without downtime. Twelve thousand sites of redirect-map, schema-preservation, and DNS-cutover practice.
- Legacy CMS Migration Drupal, Joomla, and TYPO3 estates modernised to Astro or Next.js with rankings intact. Honest routing between modernising and upgrading in place.
Grow
Search visibility for Google, and for the AI assistants that now answer first. Audits, fixes, and pages at scale, all behind quality gates.
Discuss your project- Technical SEO Audit and remediation across crawl, index, schema, Core Web Vitals, hreflang, and AI search citability. Built for Google blue links and for AI Overviews, ChatGPT, and Perplexity.
- Web Performance Optimization Core Web Vitals fixed on Chrome UX Report field data, not a lab score. Images, fonts, scripts, server time and third parties, on the stack you already run, with a budget that keeps it fixed.
- Programmatic SEO Implementation Programmatic SEO that survives the Helpful Content Update. The HostList playbook applied to your structured data, quality gates, schema, internal linking at scale.
Brand
A name that clears the register. The domain to match. And an identity system your team can apply without having to ask.
Discuss your project- Naming and Domain Acquisition Company and product names are screened before you see them. I check for trademark conflicts, meanings in other languages, and collisions in AI search. If the .com is taken, I find the owner and buy it for you.
- Branding and Logo Brand identity, logo design, and trademark workflow for founders past the Fiverr stage and short of a six-month studio engagement. Through Brandy HQ.
Run
Independent advice for the decisions still ahead, and AI agents, automation and search work, from someone who has shipped the alternatives.
Discuss your project- Web Design Consultant Independent senior advisory on what to build, which stack fits, and which agency to hire. No build capacity to fill, so the recommendation is the recommendation.
- AI Consultant AI agents, automation and content pipelines, LLM and RAG integration in Next.js and Astro, and AI search optimization, from one senior consultant who builds what he recommends. Starts with a two-week readiness assessment.
how an engagement runs
Four stages, each with a deliverable and a price you see first.
-
Stack assessment
Thirty minutes on the problem at the top of your list, then a written read of the stack you have: crawl and index state, Core Web Vitals field data, the PHP and plugin surface, editor workflow and the hosting bill. You leave with a price range and a timeline whether you sign or not.
- Audit with a prioritised fix list
- Stack recommendation with the reasoning shown
- Price range and timeline in writing
-
Architecture and migration plan
What gets built, what it costs, what is out of scope, and the date, all fixed before any work starts. Framework and CMS choice, the content model, a redirect map sourced from real traffic, hosting and CI.
- Written scope at a fixed price
- Architecture and content model
- Redirect map and metadata transport plan
-
Build or migrate
Short sprints, each followed by a working preview link, so you judge progress on the real thing. SEO lint, schema validation, a Core Web Vitals budget and redirect tests run on every build, not once at the end. Cutover happens with monitoring on.
- Preview link after every sprint
- SEO linter and speed budget on every build
- Zero-downtime cutover, sitemap submitted the same day
-
Operate and measure
Either your team takes the code, the docs and the access, or I stay on. Search Console, CrUX and AI-citation tracking are read monthly against the numbers set in the assessment, and the next fixes are priced from what the data says.
- Code ownership and handover docs
- Monthly read of Search Console and CrUX
- AI Overview citation tracking
project spotlight
all workThree builds I run myself, with the numbers they publish.
-
Web hosting buyers were choosing from commission-led top-ten lists. The market needed an independent directory with an auditable ranking and enough coverage to be the reference.
Designed and built the platform: programmatic profile, country, category and comparison pages from one data model, the HRI scoring engine, verified owner claims, an AI-assisted matching flow and a streaming sitemap past 50,000 URLs.
- 30,000+companies tracked
- 60+countries covered
- 0paid rankings
-
My parents' Vedic astrology practice needed to reach readers in their own languages, without a translation team and without deploys slowing down as the catalogue grew.
Built the platform with subdirectory i18n, bidirectional hreflang and an out-of-band translation pipeline, plus programmatic SEO behind quality gates: a humanizer pass, a banned-phrase blocklist and readability floors before any page goes live.
- 125,000+pages live
- 30languages
- 93+free tools
-
A consultant's site has to prove the service it sells: fast, multilingual, and publishing every week without an agency behind it.
Astro on Supabase with a custom admin, a research-gated blog pipeline, an eight-language translation pipeline, build-time SEO lint, static search and a Core Web Vitals budget on every build. The receipt further down this page measures it live.
- 3,100+URLs in the sitemap
- 8languages
- 1engineer
why me
What you are actually buying.
- 5,000+
Almost every problem you bring is one I have already solved in production.
- 1
You talk to me from the first call to handover. No account manager, no sales layer.
- 100%
Repository, hosting and DNS in your accounts. No licence fees, nothing locked to me.
- 2
A build-time SEO linter and a Core Web Vitals budget run on every build, so regressions are caught before launch, not after.
- 3,100+
The stack I recommend is the one this site runs on, measured live further down the page.
- London
Based in London. Calls on UK time, with early-evening slots for US time zones.
this page, the receipt
Every build ships with a speed budget. Here is what this page cost your browser just now, measured live, not quoted.
- measuring
- measuring
- measuring
- measuring
- measuring
practical guides
all writingRead the reasoning before you book the call.
-
Is Astro good for SEO? What running it at scale taught me Astro is one of the most SEO-friendly ways to build a content site in 2026, mostly because of what it does not ship. Here is the honest case, and the gotchas. -
Next.js vs Remix vs Astro in 2026: which one for which business (with production numbers) Most ranking comparisons of these three frameworks are written without production data. This is the version written from running Astro and Next.js in production, with real build numbers and the trade-offs that decide the choice. -
PHP2Shell: the PHP vulnerability that argues for going headless Governments pulled sites offline on 21 October because PHP sat in every request path. Static and headless builds stayed up. Here is the decision table. -
Next.js + headless CMS in 2026: which one for which brief Most 'best headless CMS for Next.js' lists are paid affiliate placements. This is not. Sanity, Payload, Storyblok, Contentful, Strapi, Directus, Supabase, headless WordPress, picked by the brief that fits.
try before you talk
all free tools- AI citation checker Check whether AI assistants cite your site when they answer the questions your buyers ask.
- Name checker Generate a name, or test one, against trademark registers and domain availability.
- AI search keyword research See which questions AI engines answer for your topic, with volume, difficulty and the sources they cite.
fixed-scope briefs
all briefsThese 17 services are the general offers. For specific stacks and industries there are pre-scoped briefs with the starting price already written down: agentic engineering with Claude Code, Next.js + Supabase builds, Astro development, and fifteen more at the briefs index.
the long version
what stack do we build on
We build on the stack that fits your team and your brief, not a default we push regardless. The mix below covers about 95% of what we ship in 2026.
Pure modern stacks
Next.js with Sanity. Next.js with Payload. Astro with Storyblok. Nuxt 3 with Strapi or Contentful. Each combination has its own sweet spot. Sanity for editorial-heavy teams that want a customisable studio. Payload for self-hosted ownership and a Postgres-friendly model. Storyblok for marketing teams that want visual editing without leaving the CMS. Strapi for back-end engineers who want full schema control. Contentful at the enterprise tier where multi-environment workflow matters more than DX.
Bespoke and SaaS
Next.js with Supabase or Postgres for the database, Stripe for billing, Vercel for deployment. Real-time interfaces, dashboards, marketplaces, and B2B SaaS where a CMS is the wrong primitive. We built HostList.io on this stack, a directory of 30,000+ web hosting companies with full search and filter, so the operating playbook is battle-tested.
What we do not build
We do not build on Wix, Squarespace, or Webflow at agency scale. We are happy to migrate you off any of them. We do not build mobile apps; that is a separate practice. We do not do paid media management; we partner with specialists when an engagement needs it.
why work with us instead of hiring in-house
Hiring in-house is the right answer when your roadmap is so dense that one or two engineers, fully embedded, will be heads-down for 18 months. For everything below that bar, an outsourced senior team is faster, cheaper, and lower risk.
Speed
A senior agency engagement starts in two weeks. An in-house hire takes three to six months from approval to first commit, plus another two months before the new engineer has the institutional context to ship without supervision. If your shipping window is shorter than nine months, you are the wrong size for an in-house hire.
Stack range
Most projects hit at least three of WordPress, headless, Next.js, Astro, and a CMS layer. Hiring one full-time engineer for that range is hard; hiring four to cover it is expensive. An agency team gives you senior practitioners across all of them at the cost of one mid-level salary.
Risk
The engagement ends when the project ends. An in-house hire that does not work out costs six to nine months of severance, ramp-up, and search costs. The agency model swaps that for a clean line item.
Where in-house wins
Long-running product teams with a multi-year roadmap and a brand-defining web product. If that is you, hire in-house and use us for spike work. If it is not, outsource is the better economics.
what does an engagement look like
Three phases, fixed scope, written SOW. Same shape across every service.
Phase 1: discovery
A 30-60 minute call covering goals, audience, stack, timeline, and budget. You leave with a stack recommendation, an honest range, and a written SOW within the same week. Free, no obligation, no slide deck.
Phase 2: build or remediate
Daily Loom updates from the lead engineer. Weekly mid-build review call. Tickets in Linear or your tool of choice. Repos, hosting, DNS, and CMS accounts in your name from day one. The senior engineer who took your kickoff call signs off on every PR.
Phase 3: launch and care
What is always in writing
- Inclusions and exclusions in the SOW.
- Milestones with payment terms.
- Code, hosting, DNS, and CMS account ownership in your name.
- Handover policy at no charge if you ever decide to move the codebase to another agency.
who is behind these services
Me, Gautam Khorana. I co-founded Seahawk Media in 2018 and ran its operations as COO until 2026, where the team shipped over five thousand sites. The services here are delivered by me, with specialists joining when the scope needs them.
I take every kickoff call, scope every statement of work, and stay close enough to every engagement that you do not get bounced through a sales chain. This site is my personal page, and every conversation starts with me.
I also run HostList.io, a programmatic-SEO directory of more than 30,000 web hosting companies on Next.js plus Supabase, and hosted WP Legends, an interview series with founders and operators in the WordPress ecosystem, for 156 episodes. Both inform what I recommend on client work; I do not push tools I do not actually use.
frequently asked questions
Jamstack, costs, ownership and how the work runs.
What is Jamstack development?
Building a site so that pages are rendered ahead of time, or at the edge, and served from a CDN, with content pulled from a headless CMS and anything dynamic handled by APIs. In practice that means Next.js, Astro or Nuxt on the front, Sanity, Payload, Storyblok or Contentful for the editors, and Vercel or Netlify to run it. The result is a site with no PHP in the request path: faster first paint, a much smaller attack surface, and hosting that costs about the same at ten visits or ten million.
Jamstack or WordPress: which should I choose?
They solve different problems. WordPress gives you a mature editor, a plugin for most needs and a large pool of people who know it; the trade is a PHP runtime in every request and a plugin stack that needs patching. Jamstack renders at build time or the edge, which is what gets you sub-second loads, fewer moving parts to secure and hosting that does not scale with traffic; the trade is that editors need a headless CMS and custom features need an engineer. For content and marketing sites where speed and search matter, I usually recommend Jamstack. If your workflow depends on something only WordPress does well, I will say so rather than sell you a move.
Which services do you offer?
17 services across the lifecycle of a serious website: Jamstack Development. Headless CMS Development. Web Performance Optimization. Web Design and Development. Website Redesign. Branding and Logo. MVP Development. Naming and Domain Acquisition. Site Migration. Technical SEO. Enterprise DAM Consulting. Directory Website Development. Programmatic SEO Implementation. Web Design Consultant. AI Consultant. Legacy CMS Migration. Portfolio Web Design. They can be bundled under a single engagement or scoped one at a time.
What stack do you build on?
Next.js with App Router, Astro for content-heavy sites, Nuxt for Vue-based teams, and a CMS layer that pulls from Sanity, Payload, Storyblok, Strapi, or Contentful depending on the brief. Most projects sit at one of those intersections; we pick to match the team and the brief.
What does a Next.js development agency cost?
On this site the bands are public. Hourly senior Next.js consulting from $120/hr, a fixed-price feature build from $4k, a marketing site from $5k, and a content platform with a headless CMS from $10k. Larger platforms are quoted from a written scope. Every figure is a starting price that gets fixed after a 30-minute discovery call, and you own the code at launch.
Which headless CMS should I use?
The one your editors will still be using in a year. Sanity when content is structured and the team wants real-time collaboration and a customisable studio. Payload when you want the CMS in your own repository and database, on your own infrastructure. Storyblok when marketers need a visual editor and a component library. Contentful when procurement needs an enterprise vendor with SLAs. Strapi when the team is already on Node and wants an open-source admin. I have shipped on all five and pick against your content model, not a preference.
Will my rankings drop when I move to Jamstack?
Not if the migration is run as an SEO project rather than a rebuild. The redirect map comes from real traffic in Search Console and Ahrefs, not from a sitemap export. Titles, meta descriptions, canonicals, hreflang and schema are carried across byte for byte and diffed before launch. Internal links are rewritten, not left pointing at old URLs. Cutover happens with monitoring on and the new sitemap submitted the same day. Done that way rankings hold, and the Core Web Vitals pass that comes with the new stack tends to help rather than hurt.
Can Core Web Vitals be fixed without a rebuild?
Often, yes. Most LCP failures come from an unsized hero image, a render-blocking font or script, or a slow server response, and most CLS from late-loading embeds, ads and web fonts. A technical audit from $2.5k finds which, using field data from CrUX rather than a lab score, and the fixes are usually a few days of work on the existing stack. The honest exception is INP on a page weighed down by third-party scripts and a heavy front-end bundle, where the cheapest fix is sometimes a new front-end. I tell you which you have before you spend anything.
show 10 more questions show fewer
How long does a migration to Jamstack take?
Four to eight weeks for a site under 1,000 pages: one to two weeks of audit and inventory, a week of architecture and redirect mapping, then build, content transport and QA in short sprints with a preview link after each. Larger estates scale with the number of content types, integrations and languages more than with the page count, since pages are generated from templates. Expect 30-40% of the effort to go on planning and QA rather than the build itself; that is where rankings are kept.
What does an engagement cost?
Starting prices: AI readiness assessments from $2k, branding from $3k, naming and domain acquisition from $2.5k, technical SEO and Core Web Vitals audits from $2.5k, headless CMS selection from $2.5k, site migration from $3k, Jamstack builds from $4k, web design and development from $5k, MVP builds from $10k. Specific pricing comes out of a 30-minute discovery call where we scope to your stack and timeline.
Do you sign an NDA, and who owns the code?
Yes to the NDA; send yours or use mine. Code, content and design files are yours at launch: the repository is transferred to your GitHub organisation, hosting and DNS sit in your accounts from day one, and the handover includes the documentation your next engineer needs. There are no licence fees on anything I build, and nothing is locked to me.
How do we communicate during a project?
A written update at the end of every week, a working preview link after every sprint, and a shared channel, Slack, Teams or email, your choice, for anything in between. Calls are scheduled rather than ad hoc, and you talk to me, not an account manager. Scope changes are written down and priced before they are built.
Can you do everything end-to-end or just one service?
Both. Most engagements start with one service, a migration, an audit, a new build, and expand into the others as work surfaces. Some clients book several from the start as a single bundle, which is the fastest way to get a new site shipped and sustained without coordinating multiple agencies. Either model works.
How are you different from a freelancer or a generalist agency?
Three things. First, we are senior-led across every project, the engineer leading your build is the same engineer who signs off on every PR. Second, I have been behind 5,000-plus sites, which means almost every problem you bring is one I have solved before. Third, we work across the full stack range, static and headless through to bespoke applications, so we never recommend a tool we do not actually use.
Do you help with enterprise DAM platforms?
Yes. I run independent DAM projects: requirements, platform selection, metadata and taxonomy, scripted migration and integrations, on whichever platform fits. No vendor pays me for a recommendation. A custom DAM built on Next.js, Supabase and object storage is an option when no vendor fits, but it is rarely the first answer.
Do you build directory and listing websites?
Yes. Programmatic-SEO directories on Next.js plus Supabase, with the SEO and data-quality patterns that keep large sites indexed. I built and operate HostList.io, 30,000+ web hosting companies ranked on this exact stack since 2024, so the playbook is battle-tested. We handle industry directories, location directories, tool directories, and people-and-service directories.
Where are you based?
I am based in London and work with clients across the UK, Europe and the US. Calls run on UK hours, with early-evening slots for US time zones. Specialists join when the scope needs them, and you keep one point of contact the whole way through: me.
Who does the work?
Me, Gautam Khorana. I co-founded Seahawk Media and ran its operations as COO until 2026, and I have shipped 5,000+ sites. I scope, design, build and ship the work myself; specialists join for illustration or legal review when the scope needs them, and I stay on it until it ships. There is no sales funnel between you and the person who does the work.
next step
Fix what slows your site down.
A few lines about the site and the problem at the top of your list is enough. By the end of the first reply you will have an honest read on fit, a realistic timeline, and a price range whether you sign or not. If I am not the right fit I will tell you who is.