Pricing Strategy Founder Brief

Prepared: July 10, 2026
Status: Revised after buyer value recalculation

Decisive recommendation#

Do not launch at $75,000 plus $12,000 monthly. The corrected value model does not support that as the default for a 75 to 300 property manager.

Launch a tightly standardized premium offer at:

The monthly partnership is not automatic. Offer it at day 75 only when the client and Taylor identify at least 2.5 times its fee in distinct, conservative, post implementation annual value. If that value is absent, the correct conversion is no retainer, not a cheaper managed tier.

For at most three founding design partners, display the Standard list price and apply a one time $5,000 implementation credit. The effective price is $35,000 plus $5,000 monthly if the client elects continuation. Do not discount the recurring price.

This is not a lower priced version of the original bespoke promise. Standard must use supported connectors, a standard client owned deployment, a canonical model covering no more than four domains, and one accelerator selected from a defined catalog. Novel connectors, custom applications, private deployment, and continuous embedded engineering are higher band or separately scoped work.

Why the original recommendation failed#

The prior model started with delivery cost and premium consulting comparables, then checked affordability. That showed what a senior team might need to charge, but it did not prove what this specific buyer could earn.

It also overstated customer value in three ways:

1. Booking and retention gains were counted as company revenue instead of contribution profit.
2. Every labor hour saved was treated as cash value, even when the time would merely be redeployed.
3. No causal attribution, first year timing, or overlap discount was applied.

Using the base operating assumptions, the correction is material:

The base case assumes one labor hour saved per property per month, 50% cash realization, a 3% booking uplift with 50% attribution, a 2 point retention improvement with 50% attribution and first year timing, then a 20% overlap haircut.

A strong case produces about $50,100, $100,200, and $200,500 at 75, 150, and 300 properties. Even that does not automatically support both implementation and an ongoing retainer because the same benefit cannot be sold twice.

The corrected value formula#

Count only value that can reach the client income statement or cash flow:

Realized labor value =
properties x hours saved per month x 12 x loaded hourly cost x cash realization

Booking value =
portfolio booking revenue x uplift x company yield x contribution margin x attribution

Retention value =
retained properties x annual contribution per property x first year timing x attribution

Net operating value =
(labor + booking + retention) x (1 - overlap haircut)

Add trigger value only when documented from client records. Valid triggers include a funded hire actually avoided, a scheduled migration, a vendor contract removed, an acquisition integration, or expected loss reduction based on historical incidents.

Do not count gross booking value, gross management revenue, unused staff capacity, generic strategic optionality, or cleaner data by itself as hard dollar value.

What each price requires#

Use a minimum 2.5 times value to fee test, with 3 times preferred for a new category.

The first 12 calendar months include the 90 day implementation and nine retainer payments, not 12. A complete implementation plus 12 retainer months spans 15 calendar months.

Implementation and recurring value need separate ledgers:

Implementation fee ceiling =
(initial accelerator value + one time trigger value) / ROI target

Annual retainer ceiling =
distinct post day 90 value caused by continuity and new improvement cycles / ROI target

The original accelerator continuing to work does not automatically justify the retainer. Taylor must show what the managed partnership preserves that would otherwise be lost, or what additional value its next improvement cycles create.

Who can plausibly buy#

At the report's base assumptions, a 75 property company has about $938,000 of company revenue and $113,000 of normalized EBITDA. A 150 property company has about $1.875 million of revenue and $225,000 of EBITDA. A 300 property company has about $3.75 million of revenue and $450,000 of EBITDA.

The implications are direct:

• A typical 75 property manager is not a target for the premium partnership. Only a concrete migration, hiring, acquisition, or risk trigger could make it rational.
• A healthy 150 property manager may support the Standard implementation when the accelerator has a strong, documented outcome. Generic recurring value is usually insufficient.
• A healthy 250 to 300 property manager is the practical center of the initial market, but still needs a real value ledger.
• Low margin operators are poor prospects regardless of property count.

The offer should therefore keep the 75 to 300 property thesis as a discovery range, but concentrate outbound and proposal testing on the upper end and on trigger events.

Delivery economics#

The original 300 hour Standard scope cost about $47,500 and could not meet the corrected buyer ceiling. It is credible for a first bespoke client, but not as the repeatable unit.

The revised Standard unit contains 154 client specific hours:

At $40,000, implementation contribution before acquisition cost is $15,380, or 38.5%. Standard monthly delivery is capped near 17 hours and $2,430 of capacity cost. At $5,000, recurring contribution is $2,570, or 51.4%.

During the first 12 calendar months:

The implementation also works as a standalone sale. After $24,620 of delivery cost and $5,000 of acquisition cost, it contributes $10,380. That matters because continuation is optional and must never be required to rescue an underpriced implementation.

Scope boundaries that make Standard credible#

Standard includes:

• One client owned deployment using the standard cloud topology.
• One supported PMS connector and one supported secondary connector.
• Up to four canonical domains and 24 months of supported backfill.
• Standard synchronization, retries, lineage, quality checks, backup, access control, and monitoring.
• Standard export plus one API or webhook surface.
• One legal entity and one operating region.
• One catalog accelerator with one workflow, one primary user group, one information surface, and no more than one controlled writeback path.
• Two user acceptance cycles, documentation, training, and handoff.

Standard excludes new connector development, indefinite browser automation, custom applications, multiple workflows, multiple entities, private or local deployment, 24 hour support, and an accelerator invented from scratch.

An internal alarm triggers if Standard exceeds 180 client specific implementation hours, 85 engineering hours, $28,000 of client specific capacity cost, or 20 recurring service hours in a month. Extra production work requires a fixed scope addendum.

Contract mechanics#

• Master agreement plus a fixed 90 day implementation order.
• Bill 50% at signature, 30% at blueprint acceptance around day 30, and 20% at production acceptance or day 90 if client delay caused the hold.
• The deposit is nonrefundable after the kickoff capacity is reserved, subject to a short cancellation window before work begins.
• Hold the day 75 value and roadmap review. The client may elect a six month initial recurring term beginning on day 91.
• Recurring billing is monthly in advance. After the initial term, renew for 12 months unless either party gives 60 days notice.
• Material cloud, model, SMS, telephony, storage, and third party costs pass through at invoice cost with prior budget alerts. Ordinary internal tooling stays inside the fixed fee.
• Support is business hours with severity definitions. No 24 hour operations or unlimited development is included.
• Apply an annual increase of the greater of 4% or CPI, capped at 8%, with separate rebanding for real complexity changes.

Willingness to pay validation#

Run 20 financially qualified interviews and issue 12 real proposals within roughly 120 days. Do not ask whether the idea sounds valuable. Ask:

1. What cash expense, approved hire, owner churn, migration cost, or revenue constraint is this solving?
2. What did that problem cost during the last 12 months?
3. Which part of that cost would disappear in cash, and which part would merely free capacity?
4. What evidence would your CFO accept as causal?
5. What one time result would make a $40,000 implementation rational?
6. What separate annual result would make a $5,000 monthly partnership rational after day 90?
7. Who owns the budget and what is the approval path?
8. If the proposal were issued today, would you pay the deposit this quarter?

Reserve the $35,000 implementation for no more than three prospects that meet the design partner requirements. Randomly assign the remaining matched Standard prospects between the ordinary price cells rather than showing a menu:

• Up to three design partners at $35,000 plus $5,000 monthly, requiring $87,500 of implementation value and $150,000 of distinct annual recurring value.
• Ordinary Standard cell A at $40,000 plus $5,000 monthly, requiring $100,000 and $150,000 respectively.
• Ordinary Standard cell B at $50,000 plus $7,000 monthly, requiring $125,000 and $210,000 respectively.

Advance only if at least four of 12 proposals produce paid deposits, median discount stays at or below 12.5%, at least two of the first three clients elect continuation, and measured client value reaches at least 1.5 times fees during early delivery with a credible path to 2.5 times.

Barbell implications#

The premium arm can finance the future low cost data independence layer only after repeatability is proven. A mature Standard client produces about $33,500 of first 12 month contribution after modeled acquisition cost. Roughly eight mature Standard clients fund one $219,000 fully loaded senior engineer, with little room for central security and infrastructure. Use ten clients as the practical planning threshold for that hire.

Do not introduce a $1,000 to $3,000 monthly managed service. That is the money losing middle. A buyer either qualifies for a bounded premium partnership, buys a fixed implementation without continuing service, or eventually uses the automated low cost layer.

Kill criteria#

Redesign or abandon the model if any of these occur:

• Standard delivery remains above 180 client specific hours after the third client.
• Standard engineering remains above 85 hours once supported connectors exist.
• Standard client specific cost exceeds $28,000 twice in a row.
• Standard recurring work exceeds 20 hours monthly after the first 60 days.
• Fewer than two of the first three clients elect continuation.
• Two of the first three clients measure less than 1.5 times fees in value.
• Qualified buyers cannot document $100,000 of implementation value and $150,000 of separate recurring annual value.
• More than 25% of qualified demand requires custom applications or novel connectors, but buyers will not pay Complex or Advanced pricing.
• Buyer value ceilings remain below provider delivery floors after three to five paid implementations.

The next decision Taylor should make#

Approve or reject the narrow Standard definition. If Taylor accepts supported stack boundaries, catalog accelerators, and a 180 hour hard ceiling, test $40,000 for implementation and $5,000 monthly only after the day 75 value gate.

If Taylor wants every client to receive a new connector, custom information surface, and continuously active engineering workstream, the lower price is not viable. The original higher delivery cost was closer to reality, but the target buyer market is unlikely to support it. In that case, move above 300 properties or change the offer rather than inflating the value calculation.