turn approved client content into a build‑ready package.

DUSK Handoff gives web agencies a structured, versioned handoff between client approval and website development.

See how it works

14-day free trial, no card. Then £99 a month.

Home page

Client content

Business name: Harbour & Hearth Bakery
Tagline: Sourdough baked before the harbour wakes
Opening hours: Tue–Sat, 7:00–15:00
Logo: harbour-hearth-logo.png · alt text added

Build package

v2 · complete

dusk-handoff-export/
manifest.jsonversion 2 · complete
content/
home.md
contact.md
data/
content.json
assets.json
assets/images/
home-logo-harbour-hearth-logo-3f9a1c2e.png

Illustrative example: approved fields from a fictional bakery become files a developer or coding agent can use.

The gap after sign-off

DUSK Handoff is built for the step between a client approving their content and a developer being able to use it.

The client has approved the content, but it's spread across emails, documents and shared folders.
Images arrive with names like IMG_4021.jpg and no alt text.
Someone has to copy, rename and reorganise everything before development can start.
When a field changes after sign-off, it's hard to say which version was approved.
Coding agents need structured input they can trust, not a pasted email thread.

How it works

Five steps from an empty project to a package your developers can build from.

Create a project
Pick a reusable content template and mark which fields this client must complete.
Send a secure link
The client opens it on any device, without an account. Links expire and can be revoked.
The client adds content and files
Progress saves as they go. Outstanding and invalid fields are listed, so nothing is missed.
Review and approve
Approve, reject or request changes on each field. The client sees only your notes for them.
Export the package
An immutable approved version becomes a ZIP of Markdown, JSON, files and a manifest.

Built around approval, not just collection

Every part of the workflow keeps track of what was approved, by whom, and in which version.

For your clients

Mobile-friendly submission: One focused form per page, with autosave and a clear list of what's left.
Changes in context: Each requested change sits on its field, with your note, not in an email.

For your team

Reusable templates: Start from a five-page website template and duplicate it for your own.
Field-level approval: Every decision applies to a specific revision; newer client edits need a fresh look.
Versioned snapshots: Approved versions never change. New edits make a new version.

For your developers

Markdown and JSON: The same approved content in both forms, with a documented schema.
Asset traceability: Every file keeps its original name, a safe filename, dimensions, alt text and a checksum.
Predictable structure: Stable paths and a manifest that says exactly what's complete and what isn't.

What your developers receive

Every export is a ZIP built from one approved version. This example is illustrative, and the format may evolve with a new schema version.

dusk-handoff-export/
  manifest.json
  README.md
  content/
    home.md
    about.md
    services.md
    service-detail.md
    contact.md
  data/
    content.json
    assets.json
  assets/
    images/
    documents/

{
  "schemaVersion": 1,
  "approvedVersion": { "number": 2, "approvedAt": "2026-10-25T14:20:00Z" },
  "completeness": "complete",
  "pages": [
    {
      "id": "home",
      "fields": [
        { "id": "business_name", "value": "Harbour & Hearth Bakery" },
        { "id": "logo", "type": "image",
          "value": ["assets/images/home-logo-harbour-hearth-logo-3f9a1c2e.png"] }
      ]
    }
  ]
}

An excerpt of data/content.json for a fictional business.

Who it's for

Small web agencies and studios that build marketing websites for clients, plus the freelancers and developers they work with.

Client marketing websites
Multi-location service businesses
Local business websites
Portfolio and brochure sites
Projects built with Astro or Next.js
Projects where a coding agent builds from approved content

Simple pricing

Try the whole journey free for 14 days. Subscribe when you need more projects, your team, file uploads or GitHub.

	Free trial	£99 a month
Projects	1 at a time	Unlimited
Team members	Just you	Unlimited
Client file and image uploads	Not included	Up to 25 MB per file
GitHub integration	Not included	Included

Full pricing and plan details

Questions

What is DUSK Handoff?

A tool for web agencies that collects content from a client through a secure link, lets your team review and approve it field by field, and turns the approved version into a structured package: Markdown and JSON content, the client's files and a manifest. Developers and coding agents build from that package instead of from email threads and shared folders.

Does it replace a CMS?

No. DUSK Handoff covers the step between client approval and development. The package goes into your own build and your own CMS, if you use one. It does not host, edit or publish a website.

Does it build websites automatically?

No. It hands your developers approved, structured content. If you connect GitHub, a new repository can start from a small Astro starter that already reads the package, and later versions arrive as pull requests for you to review. It never merges, deploys or publishes anything.

What does the export contain?

A ZIP with a manifest (version, approval details, completeness, warnings and a checksum for every file), one Markdown file per page, the same content as JSON, an asset manifest with filenames, sizes, dimensions, alt text and checksums, the files themselves and a README. Only approved content is included. If something required isn't approved yet, the package says so.

All questions

Hand your next build a package, not a pile.

Run one real project through the free trial, or ask for a walkthrough.

Book a walkthrough