The Value Bureau View products
Menu
Back to method archive
VB-M005 Provisional E0

Concierge workflow before software

Deliver a repeatable workflow manually before investing in software, so real inputs and failure cases define the product.

Created 2026-06-22Updated 2026-06-22By Method ID VB-M005
Provisional record. A structured hypothesis with a named buyer, mechanism, first test, and guardrails. No market evidence is claimed. Structured hypothesis only.

Economic job

Buyer, problem, and value

Buyer
A team or operator with a repeated workflow that is painful enough to pay for, but not yet understood well enough to automate safely.
Problem
Software built from assumptions can automate the wrong step, miss edge cases, and hide whether the buyer values the outcome.
Value created
Manual delivery exposes the true workflow and tests the result before code becomes the expensive commitment.

Method

Operating sequence

  1. Choose one repeated workflow with a measurable before and after state.
  2. Sell or recruit a small manual pilot.
  3. Perform the workflow using checklists and lightweight tools.
  4. Record every input variation, exception, review step, and buyer correction.
  5. Automate only the stable steps that repeat across paid pilots.

Economics

How value is captured

Pricing basis
Charge for the completed workflow outcome during the concierge phase.
Capital required
Low
Time to first test
One to two weeks
Fulfillment load
High

Revenue models

  • paid pilot
  • setup fee
  • software subscription after proof

First test

Three paid manual pilots will reveal a stable workflow and a repeated willingness to pay before software is built.

Setup

  1. Define one workflow and output.
  2. Recruit three buyers in one vertical.
  3. Deliver manually with a visible work trail.
  4. Measure time saved, corrections, and repeat intent.

Primary metric

paid_pilots_completed

Budget cap

No custom software build before paid manual evidence.

Scale

Automate stable steps after 3 paid pilots show the same core workflow and repeat intent.

Iterate

Narrow the vertical or outcome when inputs and review needs vary too widely.

Archive

Do not build software when buyers will not pay for the manual result or the workflow does not repeat.

Distribution and capability

Inputs

Channels

  • direct outreach
  • existing client base
  • vertical landing page
  • partner referrals

Skills

  • workflow mapping
  • manual operations
  • customer discovery
  • basic automation

Tools

  • intake form
  • checklist
  • spreadsheet or database
  • automation tool later

Compounding asset

What remains after the test

A verified workflow model, exception library, training examples, and an initial customer cohort.

Method priority scores
Speed3 / 5
Capital Light4 / 5
Codex Leverage4 / 5
Feedback Speed4 / 5
Margin3 / 5
Risk Control5 / 5
Defensibility5 / 5
Strategic Fit5 / 5

Risk controls

What can break the method

Manual delivery can become an unprofitable service.

Control: Track fulfillment minutes and stop adding scope outside the defined workflow.

A small sample can hide edge cases.

Control: Keep the first automation reversible and retain human review until exceptions are understood.

Source trail

Why this record exists

  • Mission Briefdocs/00-mission-brief.md

    Places micro-SaaS after repeated demand signals.

  • Economic Value Librarydocs/08-economic-value-library.md

    Defines concierge MVPs as the first test for software methods.

Experiment history

Observed contact with the market

  • No completed Value Bureau experiment

    This record remains at its current evidence grade until a test is logged.

Current archive decision

Keep as the software gate.

The archive should not treat code as evidence of demand.

Apply the structure

Build a private card for your version of the method.

Export the buyer, mechanism, first test, risk, and stop rule before expanding the work.

Build a method card