ZeroTwo for fractional executives

Prompts for fractional executives

You are the whole delivery team, and the work you bill for is not the work that takes the time. These prompts cover the unbillable half — proposals, onboarding packs, monthly reports — so business development does not stop while you deliver.

Written in your format
Scope and exclusions made explicit
You sign off before anything sends

Prompts for fractional executives

How do I turn a discovery call into a proposal?

Mirror their problem in their own words, then phase the scope and make the exclusions explicit.

The promptThe discovery call went well and they want something in writing. Draft the proposal in my format: their problem in their words, my approach, phased scope, explicit exclusions, milestones and pricing.

Call_notes.md

How do I write a scope of work that protects me?

A proposal persuades; a SOW defines. The exclusions and acceptance criteria are what stop scope drifting.

The promptTurn this agreed proposal into a statement of work: tasks, deliverables, acceptance criteria, responsibilities on both sides, payment schedule, and what is explicitly out of scope.

Proposal_agreed.docx

How do I sense-check my pricing on an engagement?

Work back from the hours the scope actually implies, not from what feels sayable on a call.

The promptGiven this scope, estimate the realistic hours by workstream, including revision cycles and client-meeting time. Show where a fixed fee would expose me and where I should cap or exclude.

How do I plan a client's first 90 days?

A 30-60-90 plan, the information you need this week, and an agenda for the kickoff.

The promptContract is signed and I start Monday. Draft a 30-60-90 plan, the information request I should send this week, and a kickoff agenda.

Signed_SOW.pdf

What should I ask a new client for up front?

Ask once, in a single list, for everything the first month depends on.

The promptBased on this scope, write the information and access request for a new client: documents, data, systems, and the people I need thirty minutes with. Group it so they can delegate it.

How do I get up to speed on a new client fast?

Read everything they have already produced and map what exists against what the engagement needs.

The promptRead these documents and give me a current-state map: what exists, what is missing against the scope, what contradicts, and the five questions I should ask in week one.

Client_docs.pdf

How do I stop re-explaining each client from scratch?

Write the standing context per client once and reuse it on everything you run for them.

The promptRead this project and write the standing context for this client: their business, the engagement scope, my method, decisions already made, and what is out of scope. Reuse it on everything I run here.

How do I write a board update a founder will read?

Lead with the decision you need, not with the activity you did.

The promptTurn this into a one-page update for the founder: what changed, what it means, the decision I need from them, and what happens if it slips. No activity log.

Month_notes.md

How do I write a handover so the work survives me?

Document the method and the decisions, not just the outputs, so the next person can run it.

The promptWrite a handover pack for this engagement: what I built, why the key decisions were made, how to run each recurring process, and what will break first if nobody maintains it.

How do I write a monthly retainer report?

Short, client-facing, and about outcomes — readable in two minutes.

The promptWrite the monthly report for this retainer client: what I did, what it moved, what is next, and anything I need from them. Written so a CEO reads it in two minutes.

Activity_log.csv

How do I regenerate last month's report without rebuilding it?

Keep the reporting contract, update the evidence, and surface what changed.

The promptSame format as last cycle. Update the evidence, tell me explicitly what changed since last month, and flag anything that needs my interpretation before it goes out.

Last_report.docx
This_month.xlsx

How do I show a client the retainer is worth renewing?

Tie the work to the outcomes they care about, and be honest about what has not landed yet.

The promptAcross these months of work, build the renewal case: what was delivered, what measurably changed, what is still in flight, and what I would do differently next term. Do not overstate anything the data does not show.

Prompts are starting points. Filenames shown are placeholders — attach your own.

In short

ZeroTwo is an AI workspace for fractional executives and independent operators running several clients at once. It turns call notes into a proposal, a signed contract into a 90-day plan, and a month of activity into a client-ready report — keeping your format, your method and your judgment on the parts that matter.

How a prompt becomes a deliverable

A prompt starts the work; it is not the work. Every card above runs the same four beats, and stops in the same place.

Inputs, as they are

Transcripts, exports, the client's own documents, last cycle's deck. No re-typing or restructuring first.

A plan you can adjust

ZeroTwo shows what it intends to do. You set the source boundaries before it starts.

Assembly, with sources kept

Claims stay tied to the line they came from. Gaps and conflicts are surfaced, not smoothed over.

A first-review artifact

Complete enough to review against a written standard. Not a signed deliverable.

ZeroTwo stops at the judgment

The approval boundary is a product feature, not a disclaimer. ZeroTwo does the assembly. You keep the part the client is actually paying for.

ZeroTwo does

Gather and organise the inputs
Extract, theme and cross-reference
Keep every claim tied to its source
Surface gaps and contradictions
Format to your conventions

You do

Set the source boundaries
Resolve the contradictions
Verify the arithmetic
Write the recommendation
Sign it and send it

Against what you are doing now

Approach	Where it works	Where it breaks on a deliverable	ZeroTwo's difference
General chat assistant	Fast answers, flexible, already paid for	Stops at a draft. fractional operators own the path across files, slides and sheets, and re-explain the project every session.	Context and sources persist across the whole engagement
Specialist point tool	Deep fit for one format or step	Work fragments across the rest of the process; each tool holds a different half of the context.	One accountable path from inputs to artifact
Doing it by hand	Trusted method, clear accountability	Senior time goes to production and cleanup; recurring work restarts from memory each cycle.	The second run reuses the first run's method
A contractor	Human judgment, flexible capacity	Lead time and context transfer exceed the window when the deadline is days away.	Available at the moment the brief lands

Questions fractional executives ask first

Will proposals come out in my format?

Yes — attach your template and it is used as the structure. Your format, section order and language are saved as project context so the second proposal costs less effort than the first.

Is this safe to use with client information?

Start on public, synthetic or sanitised inputs to judge the output. When you do use real material, you set the source boundaries, and nothing leaves without you sending it.

I am one person. Is this worth the setup?

The setup is attaching your existing templates and writing the standing context once per client. If your recurring work is a monthly report and a proposal every few weeks, that pays back on the second run.

Will the output sound like me?

It follows the templates and prior work you attach. Read it before it sends — the point is a complete first draft to edit, not something to forward unread.

What does it cost for this kind of use?

Plans are credit-based, so a long proposal build and a quick question do not cost the same. See the pricing page for current tiers and monthly credit allowances.

Takeaways

The unbillable half of the work — proposals, onboarding packs, monthly reports — is where this pays back.
Your templates and standing context are reused, so the second run costs less than the first.
Scope, exclusions and acceptance criteria are made explicit rather than left implied.
Nothing sends without you reading and signing it.