Sanity logo

Sanity development, structured content with a live editing experience.

Sanity Studio set-ups with visual editing and live preview, powering fast websites and apps from one structured content source.

Fixed quote in 48 hoursNDA on requestYou own the code
schemas/caseStudy.tsRunning
export const caseStudy = defineType({
  name: "caseStudy",
  type: "document",
  fields: [
    defineField({ name: "title", type: "string", validation: (r) => r.required() }),
    defineField({ name: "client", type: "reference", to: [{ type: "client" }] }),
    defineField({ name: "results", type: "array", of: [{ type: "metric" }] }),
    defineField({ name: "body", type: "array", of: [{ type: "block" }, { type: "image" }] }),
  ],
});
Schema deployedPreview wiredEditors invited
SanityNext.jsAstroReactTypeScriptVercelStrapi
Sanity and the stack around it
NDA signedBefore any code is shared
Demo every sprintOn a staging link you can click
48 hrsto a fixed quote after the first call
~5 daysfrom brief to first commit
1–2 wkssprints, each ending in a live demo
100%code ownership once the work is paid for
What we build

Sanity, put to work.

The kinds of Sanity projects clients bring us most often.

Custom Studio set-ups

Editing screens shaped around how your team works.

Live preview & visual editing

Click any text on the site to edit it in place.

Headless websites

Next.js or Astro front-ends with instant publishing.

Localised content

Field- or document-level translations.

CMS migrations

Move content from WordPress or another CMS with redirects.

Reusable content blocks

Page builders that keep the design consistent.

Is it right for you?

When Sanity fits, and when it doesn’t.

We recommend the stack that suits the job, even when that means suggesting something else.

A strong choice when
  • Editors want to see changes live before publishing
  • Content is reused across several pages, sites or apps
  • You prefer a hosted CMS with no server to maintain
Think twice when
  • You must self-host everything on your own servers
  • A simple brochure site that rarely changes

Not sure? Tell us about the project on a free call and we’ll give you a straight answer.

The stack around it

Works best alongside these.

What we most often pair with Sanity. Each has its own page.

How it works

From first call to first release.

  1. 30 minutes, free

    Discovery call

    You explain the goal. We ask about users, deadlines and what already exists.

  2. Within 48 hours

    Proposal & fixed quote

    Scope, Sanity architecture, timeline and price in writing.

  3. Every 1–2 weeks

    Sprints with demos

    Working software on a staging link at the end of every sprint.

  4. Launch week

    Launch & handover

    Go live together, then receive code, docs and a walkthrough.

Timings are typical and depend on scope. Your proposal states the exact plan. See how we work.

FAQ

Questions, answered.

More about hiring Sanity developers, pricing and ownership.

Browse all FAQs
Is Sanity expensive?

Its free plan suits many small sites, and paid plans scale with users and usage. We estimate the cost for your team size before you commit.

Can our marketers build new pages?

Yes. We set up reusable blocks so they can assemble new pages from approved sections without breaking the design.

How quickly can Sanity developers start?

Usually within about five working days of agreeing the brief. You get a fixed quote within 48 hours of the first call, and work starts once the contract and NDA are signed.

How do you price Sanity work?

Scoped projects get a fixed price split into milestones, each paid when you approve its demo. For ongoing work you can hire dedicated developers monthly or by the hour. Current rates are on our pricing and hire-developers pages.

Who owns the Sanity code you write?

You do, once the work is paid for. Repositories and cloud accounts are set up in your name from day one, and you receive documentation and a recorded walkthrough at handover.

Can you take over an existing Sanity project?

Yes. We begin with a short audit of the code, hosting and open issues, share what we find in plain English, then agree a plan before changing anything.