Quartermaster — One part of your business that no longer depends entirely on you
Draft for review — v2 · Restyled to the qmaster.io design system. Dashed blocks need content from Quartermaster.

You didn't start
a business.
You built yourself
a very demanding job.

For founders who found their niche, filled their calendar, and became the thing holding it all together.

You found
the clients.

You proved
the demand.

You built
the work.

3 5 7 CLIENTQUESTION DECISIONNEEDED TEAMUPDATE FIRE TOPUT OUT NEWREQUEST FOLLOWUP
01

The Catch-22

You need capacity to fix the business. But you need to fix the business to create capacity.

  • So the process stays messy.
  • The handoff keeps waiting.
  • The decisions keep coming back to you.
  • You keep jumping in because, for now, that feels faster than stepping back.

That is the cycle.
We help you break it by starting with one function.

Need capacity to fix the business Need to fix the business to create capacity
02

Out of Your Head

We help you identify one recurring process, workflow, decision, or responsibility that keeps pulling you back in.

Then we map it, clean it up, document it, and turn it into a usable operating asset.

Something clearer now.

Something easier to improve later.

Something ready to hand off when the time comes.

03

What Done Means

Mapped

We can see how it works today.

Documented

Someone can follow it without starting from scratch.

Owned

There is a clear owner.

Tested

It has been used in real work.

Released

The asset belongs to your business.

That is the asset.
One piece of your business no longer lives entirely in your head.

04

What You Get

You walk away with one completed operating asset for a specific business function.

Depending on the function, that may include a process map, cleaned-up workflow, ownership clarity, decision rules, checklists, templates, handoff documentation, failure points, and a tested final asset your business can keep using.

We do not become the system.
The asset works whether or not we are still here.

OPERATING ASSET
05

How It Runs

Six to eight weeks, start to finish. You will know at every stage what has moved and what has not.

WEEKS 1–2
Mapped
We follow the function as it actually runs today — including the parts that only exist in your head and have never been written down.
WEEKS 3–4
Documented
Written so someone else can follow it cold. Not just the steps, but the decision rules and why each call gets made the way it does.
WEEK 5
Owned
A named person takes it on, with the authority to run it. This is the step most handovers skip, and it is why most handovers fail.
WEEKS 6–7
Tested
It runs in real work while you are still close enough to see what breaks. Whatever breaks gets fixed before we finish, not after.
WEEK 8
Released
The asset belongs to your business. We step out. It keeps running.
Placeholder — Quartermaster to confirm

Is six to eight weeks right?

The timeline above is a working assumption, built to match the five states in "What Done Means" and to make the payment split legible. Francis should confirm the real duration before this page goes live — a founder cannot commit $5,000 to an open-ended engagement, so this is the highest-priority factual gap on the page.

Needed: confirmed engagement length, and the founder's expected weekly time commitment.
Proof

Who This Has Worked For

This page currently asks a founder for $5,000 without showing them a single piece of evidence. These three blocks close that gap and are the last thing standing between this draft and a live page.

Placeholder 1 — highest priority

One anonymised before / after

A short, specific story of one function that came out of one founder's head. No client name, no logo, no permission required — which is exactly how to publish wins without waiting on formal testimonials.

Shape it like this: what the founder was personally doing every week → what was actually going wrong underneath it → what the asset changed → what they stopped doing. Roughly 120 words. Specific beats impressive; a real number of hours is worth more than an adjective.

Needed from Quartermaster: one function, one honest outcome, permission to describe it anonymously.
Placeholder 2

Who you'll be working with

A short section on Francis — not a CV, but why he can do this specific thing. Founders buy from operators, and the person is the proof when the case studies do not exist yet.

Needed: 60–80 words plus one photograph.
Placeholder 3 — optional

Organisations we've worked with

A quiet logo row. Useful if permission already exists; skip it entirely rather than showing two logos with a gap where the others should be.

LOGO
LOGO
LOGO
Needed: 3–5 logos with permission to display.

The Price

$5k

For one completed
operating asset.

The Guarantee

You are not buying hours.
You are buying a business asset.

50%

split across the engagement, while the work is being done.

50%

on release, once the asset is in your business and running.

If we do not get the function mapped, documented, owned, tested and released — you do not pay the second half.

Note — changed from the mockup

Payment terms reworded

The original visual read "50% paid monthly while we do the work / 50% paid on delivery," which does not resolve cleanly for a buyer — monthly instalments and a single delivery payment imply different structures. Reworded to "split across the engagement" and "on release" so the two halves are legible and the guarantee attaches to a defined event. Same commercial terms, no change to the deal.

Confirm this matches how Francis intends to invoice.
Questions

Before You Book

The things founders actually ask before committing $5,000.

How much of my time does this take?

Two to three hours a week, weighted toward the front. The mapping stage genuinely needs you — that is where the thinking gets extracted. Every stage after that is designed to need you less than the one before. If you are still central in week seven, we have built the wrong thing.

What if I pick the wrong function?

That is what the call is for. Most founders name the loudest problem first, and it is usually not the right one. We look for the function that keeps returning to you regardless of who else is involved — that is the one holding the rest in place.

Do you do the work, or do I?

We do the mapping, the documentation and the design. You supply the judgment being extracted, because it is yours and cannot come from anywhere else. Your team runs the test.

We do not become the system. If we did, you would have traded one dependency for another one that sends invoices.

Why $5,000, and why a flat fee?

Because you are buying a finished asset, not a block of hours. A flat fee means neither of us is watching a clock, and neither of us benefits from the work taking longer than it should. Half of it stays at risk until the asset is released.

What happens after the first one?

Some businesses stop at one, and that is a real outcome — one function permanently off your desk. Most find the second is faster, because the pattern is familiar by then and your team has done it once.

There is no retainer attached to this and no obligation to continue.

What if my process is too messy to document?

Then it is the right candidate. A function that is already tidy does not need this. The mess is not a reason to wait — it is the thing being addressed.

Let's find the first thing to get out of your head

You do not need to know the perfect starting point. That is part of the work.

On the call, we will look for the recurring process, workflow, decision, or responsibility that keeps pulling you back in — and decide together whether it is a good fit for a Quartermaster engagement.

Book a Call  →
  • 30–45 minute strategy call
  • One function
  • One operating asset
  • One part of the business that no longer depends entirely on you
Placeholder

Booking link needs wiring to the Google Calendar booking flow already connected to the Signal Check pages — a separate event type so entrepreneur bookings are attributable and do not mix with nonprofit traffic.

Draft landing page · prepared by FNL · July 2026

Build notes

Not part of the page. Delete this block before publishing.

Design system, taken from the live site

Kumbh Sans 600 for headings with −0.02em tracking · Plus Jakarta Sans 800 for buttons and UI · pink #F90695 · dark #241E29 · the four block colours #FFA0D8 / #8DEDF3 / #C69FEC / #FFE19A each paired with their matching dark tone · pill buttons at 9999px · and the signature asymmetric card radius, 24px 184px 24px 24px.

What changed from v1

v1 used a navy-and-teal palette that was close to the offer mockup but not to the website. Everything here now uses sampled values. Note the site's dark is a plum-black, not navy — that one substitution does most of the work in making the page feel like Quartermaster.

The offer stays unnamed

Per direction, the page sells the outcome rather than a product name. Worth noting the trade-off: campaigns, the email sequences and internal shorthand all need something to point at. Recommend an internal name used everywhere except this page.

Four things block publication

Confirmed engagement duration · one anonymised before/after · a short Francis section · the booking link wired to its own event type. Everything else on this page is ready.