Parallax Offer Stress Test

Fictional demonstration. Complete output from an actual local trial; no customer purchase or result is implied.

Support Reply Library Sprint: pilot-ready, with a delivery limit

Start with one $700 paid pilot and reserve a second slot only after the first has usable inputs and a workable schedule. Two clients fit the four-week time budget under your current estimates; three do not. Neither $700 nor $900 compensates all your estimated business time at $45/hour in a two-client month. Treat $700 as a deliberate learning price, not evidence of a sustainable standard fee.

Prospect-facing offer

Support Reply Library Sprint

For a small B2B software support team whose replies need clearer, more consistent wording. I review up to 60 recent, anonymised support tickets and your supplied product notes, then deliver 20 reusable reply templates and a one-page decision guide in your existing document format. Each template will state when to use it, which facts to check or personalise, and when to escalate instead of sending it unchanged.

The sprint includes one kickoff, one review call, one consolidated revision round, and a team handoff/training session. Proposed meeting limits: kickoff 45 minutes, review 45 minutes, handoff 60 minutes; preparation and follow-up are included in the estimates below. One buyer-appointed reviewer supplies a single consolidated response. A revision means correcting or refining the agreed 20 templates, not introducing a new product, new language, or a second set of ticket categories.

Pilot fee: $700 USD, proposed 50% on booking and 50% at handoff. The proposed later standard fee is $900, subject to the pilot's time and scope findings. These prices are offers to test, not proven market rates.

Delivery is within ten working days after usable, anonymised tickets, product notes, scope, and a named reviewer are in place. I will confirm dates when those inputs arrive. Please return the consolidated review within two working days of receiving the draft; delayed or materially changed inputs require a revised schedule. The delivery clock does not begin merely because a payment arrives.

The buyer checks that all 20 templates and the guide exist, cover the agreed ticket categories, match approved product facts, and include the agreed corrections. We record the handoff and any unresolved product questions. This establishes delivery, not a measured improvement in handling time or customer satisfaction.

Not included: helpdesk automation, implementation in support software, new product documentation, ongoing ticket answering, unlimited revisions, post-handoff support, or a guarantee of a particular operating result. A separate request can be scoped and quoted. Before accepting a booking, agree the cancellation/refund treatment, responsibility for factual approval, and any work required after handoff; these remain commercial terms to settle, not assumed commitments.

What the evidence supports

Do not promise a 30% handling-time reduction. A useful reply to that prospect is: “I can commit to the agreed library, guide, review round, and handoff. I cannot yet guarantee a 30% reduction. If you can supply a consistently defined baseline and comparable post-handoff data, we can plan a separate measurement exercise; the result will still depend on adoption, ticket mix, and product changes.”

Workload and calendar

Available business time = 4 × 14 =

56 hours. Less 12 hours of sales/general bookkeeping gives

44 project hours. Capacity ceilings are floor(44/15) =

2 normal clients, or floor(44/18) =

2 busy clients. Three normal clients require 45 project hours before any reserve.

I propose reserving another

8 hours, because the first freelance delivery and input quality are untested. That leaves 36 project hours, exactly enough for two 18-hour clients. Reserved time is not charged again as worked owner labour in the price calculations.

A conditional schedule is one client in working days 1–10 and one in days 11–20. Per two-week block: 18 project hours + 6 recurring-business hours + 4 reserved hours = 28 hours, matching 14/week. Stagger the starts and confirm draft/review dates before booking. The ten-day promise is feasible only if that distribution and buyer review window work; monthly capacity does not justify arbitrary overlapping deadlines. No bookings or sales are assumed.

Compare the fees

Scenario: two clients finish and pay in full in the same four-week month; 3% processing applies to all money collected. Known cash costs are $30/client and $48/month. Taxes and unknown costs are excluded.

The labour valuation is not an extra cash payment. It shows the gap to your chosen return for time. If only one client fills the month, cash surplus is $601 at $700 or $795 at $900, before labour and tax; the whole $48 fixed cost and 12 general-business hours still occur in that scenario.

At booking, two pilots collect $700 total, not $1,400. After $21 processing and all $108 known monthly/client cash costs, $571 remains before labour, tax, refunds, or other costs. Two standard bookings collect $900; the corresponding remainder is $765. This assumes all those costs fall before balances arrive; it is a conservative cash-timing illustration. A deposit remains attached to delivery obligations, not completed earnings.

For two clients, a fee that covers known costs and $45/hour across all working time is:

• Normal: ($30 + $48/2 + (15 + 12/2) × $45) / 0.97 = $1,029.90/client.
• Busy: ($30 + $24 + (18 + 6) × $45) / 0.97 = $1,169.07/client.

A possible next quote to test is $1,200 after measuring the pilot; buyers' willingness to pay is unknown. Raising price is only one option: a smaller library or less review work may be more attractive, but must change the written scope.

Your $2,500 goal needs a definition. At two fully paid clients, $2,500 cash before tax and labour needs about

$1,344.33/client. $2,500 remaining after all owner time at $45/hour needs about

$2,318.56/client normally or

$2,457.73/client in the busy case. These are arithmetic thresholds, not sales forecasts or take-home pay.

Two-week validation before a website

Hypotheses: a support decision-maker will commit $700 to this exact bounded sprint; the sprint can be delivered within 18 project hours; the team can understand and use the templates without automation work.

Days 1–3: invite the two founders and three former support-lead colleagues to a short conversation. This is five reachable contacts, a convenience sample, not a market estimate. Ask about the last reply that became inconsistent, what they did next, who approves product wording, and whether they already paid for a workaround. Do not treat friendly feedback as a sale. Show only your permitted blank structure with an original fictional ticket.

Days 3–5: present the written pilot offer to relevant decision-makers. Capture actual objections, the authority to buy, a clear decline or acceptance, and any deposit separately. Proposed decision rule: one scoped paid booking within the two-week window is enough to proceed with a single delivery test; zero bookings means revise the buyer/scope/price hypothesis after asking why, not build a website to compensate.

Days 5–10: if usable inputs and a booking arrive in time, start the pilot and log time by the seven activities, input rework, template categories, revision requests, and the buyer's delivery checks. Otherwise rehearse with your own fictional material and label it a rehearsal. Do not pretend a ten-working-day service necessarily finishes inside a two-week sales-and-validation window.

Cap the initial discovery/sample work at the planned first two weeks' six non-project hours. Keep paid delivery inside the separate project allowance; avoid unpaid custom template work to win each contact. A completed pilot at or below 18 hours, with all deliverables checked and no hidden automation request, supports the next booking. Over 18 hours, unresolved factual approval, or repeated second-round edits means change scope or price before taking another slot. One pilot does not establish repeatable demand or measured handling-time gains.

The calculations were recomputed locally and saved in calculations.json; they remain conditional on your estimates. No prospects were contacted and no offer was published.