Loop

Boring work should run itself

Proposal Microsites

Built for internal use

Good proposals deserve a better process.

We replaced static proposal PDFs with branded microsites. Each client gets a focused, password-protected page for the work, scope, and offer, backed by a repeatable process for creating, checking, and publishing it.

Boring

Another proposal squeezed into a PDF.

Copy, edit, format, export, and attach the same old file.

Important

The proposal is part of the first impression.

The client needs to understand the work and the offer.

Hidden cost

The work is scoped. The proposal still takes time.

Formatting and delivery become another job on the list.

What we built

We built a system that turns each proposal into a private client microsite. The work, scope, pricing, and next step come together in one place.

    • Trigger the build
    • Select a template

    Start the proposal

    How it works
    • npm run proposal:new generates an unguessable client slug.
    • It scaffolds p/<slug>/ from a neutral proposal template.
    • Add their branding
    • Fill in the offer

    Make it theirs

    How it works
    • The shared renderer loads client-facing data from proposal.json.
    • Internal context lives in notes/<slug>.md, outside the public payload.
    • Open it in a browser
    • Review the experience

    Review the page

    How it works
    • npm run dev serves the microsite on port 4000 and rebuilds shared CSS.
    • Local routing mirrors the production gate, hidden proposal index, and blocked private files.
    • Check every detail
    • Catch what is missing

    Check the essentials

    How it works
    • npm run check rebuilds shells and assets, then checks syntax and styles.
    • Payload validation rejects missing fields, placeholders, invalid values, and private notes exposed publicly.
    • Confirm it is ready
    • Publish securely

    Publish privately

    How it works
    • npm run proposal:publish runs the checks and requires a typed confirmation.
    • It provisions per-client gate variables, commits the proposal, and triggers the production deployment.
    • Send private access
    • Spot friction

    Share with the client

    How it works
    • Production analytics and session recording are scoped to each proposal.
    • Unlock and interaction events reveal where the client journey stalls.

The outcome

A clearer proposal experience for every client.
A faster, repeatable way to publish.

Sent sooner

Get the proposal to the client while the conversation is still fresh.

First impression

A tailored microsite arrives instead of another PDF attachment.

One clear version

The offer is easy to review, and every update stays at the same link.

Private by design

The proposal is password-protected, and access can be changed or removed.

Engagement insight

See where the client hesitates, gets stuck, or needs more clarity.

Take the step

Leave PDF proposals behind.

Send quicker, update one link, control access, and see where prospects encounter friction.

Get in touch