--- name: venture-studio-guardrails description: Hard business guardrails for client work: proposals, SOWs, scoping, pricing structures, payment terms, discovery calls, hiring, and contractor agreements. Use whenever creating any client-facing deliverable or engagement structure, or when the user mentions scope, SOW, retainers, payment schedules, or client boundaries. If in doubt, check. Not for writing the proposal copy itself: use proposal-builder or contract-and-proposal-writer; this skill is the filter it passes through. license: MIT metadata: author: TechTide AI (Alex Cinovoj) provenance: original category: Sales & RevOps --- # Venture Studio Guardrails Lessons from scaling a venture studio through 7x revenue growth. Each one cost real money or real time. They are operational constraints, not advice. Every proposal, SOW, engagement plan, or payment structure gets cross-checked against all of them before it goes out. ## The guardrails 1. **Hire for performance, not personality.** Personality is not a KPI. Define measurable deliverables before anyone joins; put milestones in every contractor agreement. Check: does the plan define "good work" in measurable terms? 2. **Zero tolerance for unaccountable team members.** One unaccountable person poisons the team. Every role gets named deliverables with dates. Check: does every person have owned deliverables and deadlines? 3. **Lead the process, never let clients drive.** Too many yeses creates chaos at scale. Every engagement defines a process the client follows: communication cadence, approval workflow, decision gates, in a "How We Work Together" section. Check: who leads, and how do decisions get made? 4. **Proactive communication.** By the time a client asks for an update, trust is gone. Weekly minimum, format and schedule written into the SOW. Check: is the update cadence specified? 5. **Discovery before solutions.** Never pitch solutions to unconfirmed problems. Discovery is a scoped phase with its own deliverable (findings, requirements, recommendations). Check: is there a distinct discovery phase before build? 6. **Scope before build.** No build starts without a signed scope document referencing validated requirements. Client wants to skip scoping: red flag, price accordingly or walk. Check: is there a scoping milestone gating the build? 7. **Scope = contract, not an idea.** A scope contains deliverables, acceptance criteria, timeline, and exclusions. "We'll figure it out as we go" is a blank check. Check: are all four present, including what is NOT included? 8. **No scope creep, enforce change orders.** "Just one more thing" compounds into weeks of unbilled work. Any out-of-scope work triggers a written change order with pricing, tracked in real time. Check: does the SOW contain a change order clause? 9. **Evaluate industry leverage before engagement.** High-value clients in low-leverage industries mean custom builds with no reuse. Assess productization potential; price pure one-offs at a premium. Check: does this create reusable assets, or is it priced to compensate? 10. **Maximum two payment installments.** Three-plus installments are three-plus chances for a client to vanish. 50/50 or 40/40/20 max; engagements past 6 months move to monthly retainer, not spread milestones. Check: more than two installments? Restructure or justify. 11. **Never pay contractors in full before delivery.** Full payment upfront means zero leverage when delivery slips. Partial upfront, remainder on verified acceptance, no exceptions for relationships. Check: are contractor payments tied to accepted deliverables? ## How to apply When producing any client-facing document, run the numbered checks above as a preflight. When a guardrail is violated, flag it explicitly with the guardrail number and a recommended fix before finalizing. Do not silently "fix" business terms the user chose; flag, recommend, let them decide. ## Verification Before delivering the document, list guardrails 1-11 with pass / fail / n-a next to each. Expect zero unflagged fails. If any check cannot be evaluated because the document is silent (no payment terms, no exclusions), that is a fail, not an n-a: the missing section is the finding. ## Completion checklist - [ ] All 11 checks run against the final draft - [ ] Every violation flagged with number and fix - [ ] Scope section has deliverables, acceptance criteria, timeline, exclusions - [ ] Payment structure is two installments or explicitly justified - [ ] Change order clause present - [ ] Discovery phase precedes any build commitment Any box unchecked: not done. Fix or say so. ## Good vs bad - Bad: "Phase 1 we'll explore the requirements together and start building what feels right, billed in four monthly parts." - Good: "Phase 1 (2 weeks, fixed fee): discovery, delivering a findings doc and signed scope. Build starts only on scope sign-off. 50% deposit, 50% on acceptance. Out-of-scope requests go through written change orders." ## Red flags (verbatim excuses, all invalid) - "This client is different, we trust each other." - "It's a small add-on, a change order feels petty." - "They want to skip discovery to save budget." - "Splitting payments five ways makes it easier for them to say yes." - "We'll define acceptance criteria once we're in the work." Each of these is the exact sentence said before the loss that created its guardrail. If a document goes out that dodges a guardrail via rewording, the guardrail is still violated. Flag it or say why not. ## Footguns - The agency-mindset trap: client says jump, scope flexes, revenue stays project-shaped. Every proposal should reinforce the studio model: structured engagements, reusable systems, leverage. - Flagging violations after signature is worthless. Run the preflight on the draft, not the retrospective. - Guardrail 9 is the one everyone skips under revenue pressure, and it is the one that determines whether year two scales or stalls.