Skip to content

Custom web development

For a defined project

One accountable person from first call to handover: architecture, build, deployment, and documentation at a fixed price.

The problem

You know what you need built. What you don’t want is a rotating team, a discovery phase that bills like a build phase, and a quote that grows teeth halfway through.

A custom build means one person scopes it, builds it, ships it, and hands it over properly, with the price agreed before anything starts.

What’s included

  • Scoping & written brief

    A short call becomes a written scope: what we’re building, what it costs, when it lands.

  • Architecture

    Boring, proven choices wherever possible; clever ones only where they pay rent.

  • Full-stack build

    Front end, backend, database, integrations: one person holding the whole picture.

  • Infrastructure & deployment

    Hosting, CI/CD, environments, and domains: set up properly, not improvised.

  • Documentation & handover

    The code, the infrastructure, the docs, and the access. All of it yours.

  • Fixed price

    The number in writing before we start is the number on the invoice at the end.

How it works

  • 01

    Scope

    We define what we’re building, what it costs, and when it lands, in writing.

  • 02

    Build

    A working demo every week. You always know where the build stands.

  • 03

    Ship

    Production deployment, monitoring, and a clean launch.

  • 04

    Hand over

    Documentation and access, structured so any competent team could take it from here.

What a written scope looks like

Example. Marrowgate Press is a made-up publisher, and every name, date and figure here is invented. The price is agreed per project, so it’s left out.

Marrowgate Press needs a new website and a private portal for foreign rights. This is the scope we’d send after the first call: what’s in, what’s out and why, when each item counts as done, and what happens if the plan changes.

Marrowgate Press: website and rights portal

Document
Written scope, version 2
Dated
Thursday 15 October 2026
For
Clare Duffy (Publisher), Ade Bello (Rights)
Live by
Friday 4 December 2026

What we’re building

A site that shows the whole list, around 180 titles in print, and keeps itself up to date from the distributor’s data feed. Behind it, an invite-only portal where foreign publishers and agents browse the rights list and request reading copies. Marrowgate’s team of four edits everything else themselves.

Not included, and why

  • Selling books directly. The distributor and bookshops handle sales; a checkout would mean stock, payments and returns for a team of four.
  • Audiobook pages. Moved out in version 2, because the audio rights for most titles are still being agreed.
  • Design of the public pages. Marrowgate’s designer supplies them in Figma; we design the rights portal and the editing screens.
  • Writing copy and negotiating rights. The editors own the voice, and the deals stay with Ade.

Price, changes and payment

The price is fixed and agreed in writing before we start. The number in this scope is the number on the invoice at the end.

If the scope changes mid-build, we quote the difference in writing before doing the work, and you decide whether it goes in now or after launch. A change can move the delivery date as well as the price. If it does, the written quote for the change says so, and nothing moves until you’ve agreed it.

Payment comes in two stages: the first when this scope is signed, the second when the site is live. This quote is valid for 30 days, until Saturday 14 November 2026.

What’s included, and when each item counts as done

Each item is accepted when its check passes on the staging site, in front of Clare or Ade at a Friday demo.

Included items and their acceptance checks

Included items and their acceptance checks
ItemWhat it isAccepted when
Book catalogueEvery title in print, with cover, blurb, formats, prices and ISBNs. Filters by genre, format and season.Every title in the feed appears, and the filters return the right books for 20 titles Clare picks.
Book data feedBook details imported each night from the distributor’s ONIX feed. Marrowgate’s own copy sits in fields the feed never overwrites.A price changed at the distributor shows the next morning, and Marrowgate’s own blurb on that book is unchanged.
Author pagesBiography, photo, books and events.Every author with a book in print has a page, linked from each of their books.
Editorial pagesHome, About, Submissions, Contact and News, built from blocks the team can rearrange.Clare builds a new News page from blocks without help.
Retailer links“Buy from” links on every book, to the bookshops Marrowgate chooses.Changing the list in the CMS updates every book.
Rights portalInvite-only login by email link, and the rights list by territory and language.An invited agent can log in and an uninvited address can’t. Each title shows the right status for its territory.
Reading copiesAde approves each request. Approved requesters get a time-limited link to a watermarked PDF.The link downloads a PDF watermarked with the agent’s name and organisation, and stops working after 14 days.
Rights activityOne screen showing who asked for what, when, and what was sent. Exports as CSV.Every request from the test run shows on screen and in the export.
Newsletter sign-upA form posting to Marrowgate’s Mailchimp audience.A test sign-up appears in the audience.
Content and redirectsAround 120 existing pages moved across, and every old book and author URL redirected.A script finds every listed page on the new site, and every old URL returns one permanent redirect to the right page.
Search and sharingTitles, descriptions, sharing images, a sitemap, and Book structured data on every title page.Every title page’s structured data validates without errors.
AccessibilityBuilt to WCAG 2.2 AA.A keyboard and screen reader pass leaves no open issues on the main templates.
Hosting and deploymentStaging and production, with a deployment on every merge.A merge to main reaches production with no manual step.
Milestones, assumptions and handover

A demo every Friday, all dates 2026

A demo every Friday, all dates 2026
WeekDemoWhat you’ll see
130 OctStaging live, the ONIX import running against the real feed, first books on screen
26 NovBook and author pages from the designs, the CMS ready to try, rights portal designs for review
313 NovHome and editorial pages, filters, retailer links, newsletter sign-up
420 NovRights portal: login, rights list, requests and approvals
527 NovWatermarked reading copies, the activity screen, content moved, redirects in place
64 DecAccessibility and device testing done, launch on the production domain, handover

Assumptions

  • The distributor gives us access to the ONIX feed by Monday 26 October.
  • The Figma files for the public pages are final by Monday 2 November.
  • Ade sends each title’s rights status as a spreadsheet by Friday 6 November.
  • Clare collects feedback after each demo and sends it as one list.

Handover, on launch day

  • The code, in a repository in Marrowgate’s GitHub account.
  • The hosting and CMS accounts, in Marrowgate’s name.
  • A README for any developer: running and deploying the site, the ONIX import, and the watermarking.
  • An editor guide for the team.
  • A guide to the rights portal for Ade.
  • A list of every third-party service the site uses, and who pays for it.

Related work

Working with Neelesh was an absolute pleasure. Not only did he flawlessly execute on every requirement we outlined, but he consistently went above and beyond to ensure the final product was exceptional. His technical expertise, attention to detail, and proactive approach make him an invaluable asset to any development project!

Harry

Owner - Money Atlas

Common questions

  • 01What does a build cost?

    Every build is quoted from its written scope, fixed, before we start. If the scope changes mid-build, we re-quote the difference before doing the work, so the invoice never surprises you.

  • 02How long does a build take?

    Weeks, not quarters, for most projects. The written brief comes with a delivery date, and across 30+ projects we haven’t missed one.

  • 03What happens at handover?

    You get everything: the code, the infrastructure, the documentation, and the access. We build so that any competent team can take over, and most clients choose to stay anyway.

  • 04Can you work from our designs?

    Yes. Figma to production is a well-worn path here. No designs? Also fine; design is one of the hats we wear.

Have something to build?

Tell us what you're working on. We'll tell you how we'd approach it.

We reply within one working day.