Each story keeps the original question, test criteria and outcome together. The founder makes the decision.
Fieldwork OS · B2B software · ROOM 1 / 7
Daddy
The founder wants one system for every field-service company. Daddy separates the buyer (operations manager) from the user (technician). The first assumption: dispatch problems are costly enough for the buyer to fund a change.
Output: buyer, user and willingness to pay are separate assumptions.
Fieldwork OS · B2B software · ROOM 2 / 7
Brainstorm
The room compares a full ERP replacement, a dispatch layer and a customer portal. A technician perspective challenges yet another app; a finance perspective exposes migration costs. They choose a dispatch layer that can run alongside the existing system.
Output: one narrow concept; integration access remains uncertain.
Fieldwork OS · B2B software · ROOM 3 / 7
Research
The founder orders a comparison of three vendors’ public integration and pricing pages, completed manually and imported with URLs, excerpts and access dates. The report finds differences in available interfaces. It cannot establish that customers will pay.
Output: a sourced research brief and an explicit gap in customer observations. These sources are fictional in this story.
Fieldwork OS · B2B software · ROOM 4 / 7
Business studio
The studio separates an operations-manager persona from a technician persona and plans direct outreach through industry contacts. Subscription, setup and reporting are three streams. A weaker-demand scenario exposes the need to cover acquisition and onboarding before expanding.
Output: editable assumptions. In the model below, 3% monthly account churn is assumed, not measured retention.
Fieldwork OS · B2B software · ROOM 5 / 7
Board · plan
The board proposes a concierge pilot using a shared schedule and manual data import. Before recruitment, the founder locks: five eligible operations managers, a 14-day window, at least two paid pilot commitments and at most four onboarding hours per pilot. No complete platform is built.
Output: a small delivery test with two predeclared criteria.
Fieldwork OS · B2B software · ROOM 6 / 7
Test · outcome
Fictional outcome: five managers receive the same offer; two pay. Each pilot takes nine onboarding hours. The payment criterion passes (2/5); the delivery criterion fails (9 > 4 hours). Neither pilot supplies renewal observations after only 14 days.
Output: booked fictional observations in the story, not proof of scalable SaaS economics or real app records.
Fieldwork OS · B2B software · ROOM 7 / 7
Decision + memory
The board recommends one integration and one customer group. The founder chooses a new iteration: test a paid onboarding package before adding reporting. Second Mind keeps the original criteria, research brief, five offer outcomes and both time logs so the failed delivery target is not rewritten.
Decision: narrow the offer. Retention and repeatable acquisition remain untested.
CareLink · two-sided marketplace · ROOM 1 / 7
Daddy
The idea is a nationwide marketplace for every maintenance task. Daddy asks which side has the urgent problem and why a supplier would reserve time. The founder focuses on property managers with small, recurring jobs in one district.
Output: two customer groups and a local supply constraint.
CareLink · two-sided marketplace · ROOM 2 / 7
Brainstorm
The room compares instant bidding, a managed booking service and a supplier directory. The supplier perspective rejects unpaid bidding; the buyer wants arrival certainty. They choose manual matching with a clear response window.
Output: a matching service, with availability more critical than traffic.
CareLink · two-sided marketplace · ROOM 3 / 7
Research
An explicitly selected own agent receives a research order via MCP: inspect public supplier terms and published service areas, returning dated sources. The founder reviews the imported report. Listed coverage is treated as a statement to check, not available capacity.
Output: a fictional source map and unknown live availability; the app has not crawled the web.
CareLink · two-sided marketplace · ROOM 4 / 7
Business studio
The studio maps buyer and supplier personas separately. Direct calls recruit supply; property-manager associations are the planned demand channel. Commission and subscriptions stay separate, and gross job value is never presented as platform revenue.
Output: a capacity-limited model. Its 70% matching rate is a fictional scenario assumption.
CareLink · two-sided marketplace · ROOM 5 / 7
Board · plan
Before launch, the board and founder lock a two-week manual test: the first 20 eligible requests in one district, at least 12 completed jobs within 48 hours, with all requests retained in the denominator. Four suppliers agree to receive requests; no software marketplace is needed.
Output: completion and timing are measured; page visits are not the deciding metric.
CareLink · two-sided marketplace · ROOM 6 / 7
Test · outcome
Fictional outcome: 20 requests, 14 accepted, 9 completed within 48 hours. Three more complete late; two accepted jobs are cancelled. The criterion fails: 9/20 = 45%, below 12/20 = 60%. Acceptance (14/20) must not be called on-time fulfilment.
Output: the local supply bottleneck is visible; more advertising would not fix it.
CareLink · two-sided marketplace · ROOM 7 / 7
Decision + memory
The founder follows the board’s recommendation to reserve supplier slots and narrow the job category before increasing demand. A new iteration will test a longer, explicit service window. Second Mind keeps all 20 request outcomes, cancellations, timestamps, source dates and the original failed pass mark.
Decision: repair supply reliability. Supplier subscription willingness remains unknown.
CycleWorks · equipment + service · ROOM 1 / 7
Daddy
The founder wants to sell, rent and service equipment for every local business. Daddy separates three decisions: buy versus rent, required uptime and willingness to pay for service. One delivery-business customer group becomes the starting point.
Output: purchase, rental and maintenance assumptions are kept separate.
CycleWorks · equipment + service · ROOM 2 / 7
Brainstorm
The room compares owned stock, supplier consignment and a service-first offer. An operations perspective highlights repairs; finance challenges buying a rental fleet before demand is known. They choose a small rental pilot using borrowed demonstration units.
Output: access to pilot equipment before a large capital commitment.
CycleWorks · equipment + service · ROOM 3 / 7
Research
The founder manually checks supplier quotations, warranty conditions and spare-part lead times and imports dated excerpts as research. Published service intervals are planning inputs. Actual downtime and labour cost still need observations from a pilot.
Output: fictional sourced cost assumptions, plus an explicit unanswered question about reliable delivery.
CycleWorks · equipment + service · ROOM 4 / 7
Business studio
The studio connects a fleet-manager persona, direct outreach and three revenue streams. Rental utilisation is a scenario, not a sales forecast. Twenty rental units at 12,000 kr tie up 240,000 kr before operation; this investment is separate from the monthly calculation below.
Output: working-capital and workshop questions beside the revenue model.
CycleWorks · equipment + service · ROOM 5 / 7
Board · plan
Before the four-week trial, the founder locks: ten eligible businesses receive the same rental offer; at least four pay for a trial; each rented unit must remain usable on at least 90% of its 20 scheduled workdays. Faults count as unavailable days.
Output: payment and operational reliability are separate pass criteria.
CycleWorks · equipment + service · ROOM 6 / 7
Test · outcome
Fictional outcome: four of ten businesses pay. Three units are usable for 20/20 workdays; one for 16/20. Total availability is 76/80 = 95%, but the failed unit reaches only 80%. The per-unit 90% rule fails despite the reassuring aggregate.
Output: demand signal, failed reliability criterion and no observations yet for annual service renewals.
CycleWorks · equipment + service · ROOM 7 / 7
Decision + memory
The board recommends a spare unit and a smaller service radius before buying stock. The founder pauses fleet expansion and chooses a repair-and-replacement trial. Second Mind retains the four payment records, per-unit daily logs, warranty excerpts and the original per-unit pass mark.
Decision: test service capacity before committing the 240,000 kr rental investment.