Solo Wedge Canvas

Find the Entry Promise

A market choice still leaves too much room to build. “Reporting for field-service companies” might become a dashboard, an integration platform, a consulting service, or a collection of unrelated features. The Solo Wedge Canvas forces one entry promise: a result for a particular customer at a moment when the result can change what they do.

Use it after selecting a beachhead market and before scoping the first product. Bring evidence, not category labels: a reconstructed workflow, the current workaround, outreach results, buying signals, and the constraints exposed by the market and founder-fit exercises.

A wedge is narrower than the eventual product, but it is not a diminished version of it. The product may eventually serve an entire operation. The wedge earns entry by solving one consequential piece of that operation well enough that customers return.

Start with the Customer’s Week

Write one short account of the painful moment. Name the person doing the work, the event that creates urgency, the current alternative, and the consequence when it fails. Use a real account when you have one; otherwise label the account as a hypothesis to verify.

“Operations teams need better reporting” offers no design boundary. A useful account sounds more like this: every Friday, an operations manager at a twenty-person field-service company turns technician notes into a client status report. She copies details from several jobs, chases missing explanations, and risks sending the client a report that cannot defend the invoice.

Now locate first value in the customer’s work. It is not an upload completing, a model producing text, or a dashboard loading. In this case, first value might be a reviewable draft that lets the manager send an accurate report without reconstructing every job herself.

Complete these sentences:

• Customer and urgent moment: When ___ happens, ___ needs to ___.
• Current alternative: Today they ___, because it still gives them ___.
• Cost of failure: When that alternative breaks down, ___.
• First value: They experience value when they can ___ and observe ___.
• Reach path: I can find the first ten relevant people through ___.

If the moment does not recur, the customer cannot judge the result, or the reach path is wishful, return to market selection or discovery. A canvas cannot repair a weak entry condition.

Draft Three Wedges

Do not let the first plausible scope win by default. Write three promises that enter the same market through different boundaries. You might narrow by customer role, workflow, trigger, geography, data source, integration, or delivery method. Every adjective must either strengthen access or remove a real delivery burden.

Use this form:

For [specific customer], when [urgent moment], we provide [observable result] from [bounded inputs or service], so they can [changed action or outcome].

For the field-service reporting idea, one candidate might produce a Friday client-report draft for operations managers from technician close-out notes. Another might check completed jobs for missing invoice evidence before the billing handoff. A third might prepare a customer update only after a delayed or disputed job. These are not three feature bundles. They are three different claims about where concentrated value lives.

Reject any promise that quietly joins several customers, moments, or results with “and.” Reject one that is attractive only because its code is easy. Keep the candidate whose pain, access, and repeated use are best supported by present evidence.

Trace the Smallest Honest Delivery

Work backward from the chosen first value. Describe one delivery from input to useful result, including the work the customer cannot see. This trace usually reveals more scope than a feature list does.

• Inputs: What exact data, access, context, or customer effort begins the delivery?
• Minimum system: What must be built, bought, borrowed, or assembled for the result to be dependable?
• Visible manual work: What will the founder do by hand, and what will the customer be told about it?
• Trust boundary: What must be secured, explained, logged, reviewed, recovered, retained, or deleted before real use?
• Failure recovery: When an input is late, an output is wrong, or delivery fails, what can one founder realistically do?
• Support boundary: Which onboarding, questions, exceptions, urgency, and support hours are included?

Manual work earns its place when it exposes repeated decisions before they are encoded. It becomes a warning when customers think it is automation, when the economics depend on invisible unpaid labor, or when every delivery requires a different procedure.

For the Friday report, the founder may initially review drafts and correct a small set of recurring note problems. That work can reveal the rules the product needs. Reconstructing each customer’s entire job history or chasing every technician would reveal a service business hiding inside the wedge.

Write the Refusal

The promise is only half the canvas. Write what the first version refuses to do:

• customers and buyers it will not yet serve;
• adjacent workflows and outcomes it will not promise;
• inputs, integrations, and data shapes it will not accept;
• exceptions and support expectations it will not absorb;
• consequential decisions it will leave to the customer.

The exclusions should survive a sales conversation. When a prospect requests an excluded integration or workflow, ask whether first value is impossible without it. If the result can still arrive with a bounded workaround, keep the exclusion. If the result cannot arrive, the request has found a flaw in the wedge rather than a roadmap item.

Turn the choice into two plain statements:

Promise: We prepare a reviewable Friday client-report draft for operations managers at small field-service companies, using technician close-out notes from one supported export.

Refusal: We do not yet collect notes from multiple systems, contact technicians, send reports automatically, defend invoices, or support live operational dashboards.

A painful refusal is not automatically correct, but a painless canvas often means nothing important has been excluded.

Choose Evidence That Can Defeat the Wedge

Activation should show that the customer reached first value. Retention should show that the result has entered repeated work. Neither is a product event chosen merely because it is easy to count.

For the report wedge, activation might be the manager reviewing and sending a draft that required less reconstruction than the current process. Retention might be supplying the next week’s notes and paying for another delivery. Compliments, wait-list signups, and a successful demo may justify another conversation; they do not show that the wedge has entered the workflow.

Finish the evidence record:

• Activation: the observable customer action that confirms first value.
• Retention: the repeated behavior, payment, or renewed commitment that supports continuing.
• Operating measure: the delivery time, correction load, exception rate, or support burden that must remain workable for one founder.
• Narrow-or-stop rule: the result and date that will trigger a narrower wedge or abandonment.
• Earned expansion: one adjacent capability, plus the repeated customer behavior required before building it.

Write the test as a decision, not an aspiration: “Run five paid weekly deliveries by 31 August. Continue only if at least three customers provide the next input without prompting, use the draft in client communication, and the founder can deliver each report inside the stated review boundary.” Choose numbers and dates from your runway, economics, and risk; this example supplies the form, not a universal threshold.

The Completed Canvas

The finished page contains one customer moment, one first value, one reach path, one promise, one delivery trace, one refusal, and one test that can lose. Read it from top to bottom and ask a final question: does every necessary piece of code, manual work, trust, support, and distribution fit inside the promise one founder is making?

If yes, the next step is a bounded customer test. If the page requires several personas, workflows, integrations, or value moments to sound compelling, draft a narrower wedge. If it looks easy to ship but the evidence would teach little about painful behavior, choose a more consequential entry point.