Borrowed

Days are to the first paying customer; cash leaves out your hours, and loaded CAC adds them at $100 an hour. Planning estimate unless a source is named: how each was set.

The decisionCopy Anchor Link

Pick the platform whose store already reaches the most of your buyers. Three tests decide it. A large share of your approved accounts run it. Its store shows demand for your job. The integration takes 40 to 80 of your hours. Find your first customers reads the share from your approved accounts.

Estimate the demand before you build. Read the store’s own search for your job with Keyword.search, and count the installs of the listings that rank: where a store hides installs, reviews × 20 to 50 is a fair estimate, so a rival with 40 reviews has about 800 to 2,000 installs. A category whose top three together show under 1,000 installs will not fill a funnel of 5 customers a month.

Build the smallest integration that delivers your core result inside the platform. List it with the job in the title and the result in the first screenshot; Make content drafts it. Ten reviews in the first 30 days set its rank, so line them up with Review requests before it goes live.

Partners shorten deals and keep integrated customers longer. Treat that as the reason to try, never as a forecast: your own store numbers replace every planning number here by week 12. Integration partners runs the partner side, and Weekly readout reads both.

The mathCopy Anchor Link

customers a month = listing views × view to install × install to active × active to paid

Planning estimate unless a source is named: how each was set.

Reachable accounts = 4,180 × 40% = 1,672, read by Pick who to sell to from the software each account's site runs.

Customers = 2,400 × 5% = 120 installs; × 30% = 36 active; × 15% = 5 paying. That is about 5 customers a month at scale from one store category, at about $300 cash a customer.

Cash CAC counts what the store takes: its 20% of a $149 customer's first 12 months after churn is $149 × 20% × 9.19 = $274, and the listing fee over a year's 60 paying customers adds $17. With $5 of data that is about $300 cash a customer.

The build is priced too: 40 to 80 of your hours is $4,000 to $8,000 loaded, spread over the first 12 months of installs: $100 a customer at 60 hours, plus an hour a week of upkeep. That is 1.9 hours a customer and $490 loaded, paid back in 4.5 months at $149, inside the $795 the price can afford. Across the first quarter that averages about 5 hours a week of yours. Marketplace listings runs the listing, and Competitor gap shows who already ranks in the store.

PlaybookCopy Anchor Link

Worked exampleCopy Anchor Link

Leaseline integrates with a property-accounting platform that 38% of its approved accounts run, read by Pick who to sell to. The store’s search for rent tracking ranks three listings with 25, 40 and 60 reviews, about 2,500 to 6,250 installs between them, and the category page shows 2,400 views a month. The build takes the founder 60 hours over 3 weeks. With no store at 30% of its accounts, it would lead with Hands-on.

Launch kit writes the listing, and the founder submits it in the store’s own console. Listing check reads it daily until it is live.

At 5% view to install, the listing brings 120 installs a month, and Silence watch follows each one to activation. 36 activate and about 5 pay, at $149 a month. Review requests asks ten design partners in its first 30 days, and its rank rises with their reviews.

About 5 customers a month from one store category, $745 of new monthly revenue, at $300 cash and $490 loaded a customer once the store's share, the listing fee and 60 build hours are counted.

When it breaksCopy Anchor Link

How your agents run itCopy Anchor Link

Each call is priced from its composition. Week 1: about 20 minutes of yours and $2.35 in calls. Week 4: about 20 minutes of yours and 1¢ in calls. Week 5: about 10 minutes of yours and 1¢ in calls. Week 6: about 10 minutes of yours and 1¢ in calls. Week 8: about 15 minutes of yours and $1.33 in calls. Week 12: about 10 minutes of yours and nothing in calls.

The month runs as a Play Mix: PlayMix.compile plans it from your hours and budget, Play.apply runs each Play, and each Play runs the compositions in its rows above. Goal.pursue is the shortcut that takes the month as one goal and records which Play each step served.

import { $ } from 'startup-builder'

const mix = await $.PlayMix.compile({ strategy: 'borrowed', hours: 4 })
for (const play of mix.plays) await $.Play.apply({ play: play.id, hours: play.hours })

// Each Play runs its compositions in weeks 1 to 4:
// marketplace-listings  pick-who-to-sell-to, competitor-gap, launch-kit

You see the plan and its price before anything runs. Sends and posts go out within the limits you set; one approval rule on a class such as send makes every action in it wait for you, and going over a limit always asks. How your agents act names every class.

Good looks likeCopy Anchor Link

Connect these firstCopy Anchor Link

Plays it runsCopy Anchor Link

ReferenceCopy Anchor Link