# .md Studios — Independent Project-Pipeline Challenger Queue **Status:** discovery only; no build authorization **Reviewer:** Brick **Positioning filter:** expensive recurring friction; named budget owner; evidence before software; transferable asset; commercial outcome remains clear with every file/cursor metaphor removed. ## Ranking logic Ideas were ranked for: pain frequency, measurable economic loss, buyer accessibility, smallest disconfirming test, low initial integration burden, and eventual transferability to an operator or strategic buyer. None advances because it sounds clever. Each must earn a receipt. --- ## 1. QuoteLeak — estimate-to-invoice margin leakage for specialty contractors ### Problem Small HVAC, electrical, plumbing, fire-protection, and commercial-service contractors lose margin between supplier quote, customer estimate, change order, field substitution, and final invoice. The data exists, but usually across PDFs, email, accounting exports, and job notes. Owners discover leakage after the job—or never. ### Target operator / buyer - **Operator:** controller, estimating manager, or operations manager at a 10–100 employee specialty contractor. - **Economic buyer:** owner/GM with gross-margin responsibility. - **Potential acquirer:** vertical field-service software, construction ERP, procurement network, or contractor roll-up platform. ### Discovery wedge A concierge audit of 20 recently closed jobs. Ingest exported estimates, supplier quotes, approved change orders, and final invoices; return a human-verified leakage ledger. No production integration and no autonomous billing changes. ### Evidence required before build 1. Ten contractor interviews across at least two trades. 2. Five anonymized closed-job packets from at least three firms. 3. Measurable unexplained leakage or missed billing worth **at least 1% of job revenue or $1,000 per audited job** in three independent firms. 4. At least two firms pay for a second audit or sign a paid pilot. 5. A controller can verify each flagged delta from source documents in under five minutes. ### Kill tests - **KILL** if fewer than 3/10 operators can provide the necessary exports without new field behavior. - **KILL** if median recoverable value is below the greater of 1% revenue or 5× the proposed monthly price. - **KILL** if more than 20% of findings require subjective contract interpretation rather than document reconciliation. - **KILL** if established accounting/field-service tools already produce an equivalent source-linked leakage report for the sampled firms. ### Why it ranks first The value is denominated in recovered gross margin, the smallest proof can be done manually, and the eventual asset has clear strategic buyers. The first product is a receipt, not a dashboard. --- ## 2. TurnReady — evidence-backed unit-turnover control for regional multifamily operators ### Problem Regional property managers coordinate inspections, repairs, cleaning, keys, utilities, photos, vendor invoices, and make-ready dates through calls, texts, spreadsheets, and disconnected property-management systems. A delayed or disputed turnover creates measurable vacancy loss, yet the evidence chain is weak. ### Target operator / buyer - **Operator:** regional maintenance director or make-ready coordinator managing 500–5,000 units. - **Economic buyer:** VP of operations or property-management owner. - **Potential acquirer:** property-management software, maintenance marketplace, inspection platform, or multifamily operator. ### Discovery wedge Run a four-week shadow ledger for 25 turnovers using existing exports and forwarded artifacts. Produce one source-linked timeline per unit: ready definition, blocker owner, promised date, completion evidence, and vacancy-cost exposure. Do not replace the incumbent PMS during discovery. ### Evidence required before build 1. Eight interviews covering onsite, regional, and executive roles. 2. Two operators provide historical turnover records for at least 25 units each. 3. At least 15% of sampled turnovers contain an avoidable delay, missing receipt, or disputed completion state. 4. The evidence ledger identifies a median of **one avoidable vacancy day or equivalent rework cost per five turnovers**. 5. One operator pays for a live shadow pilot and names the person who owns the workflow after handoff. ### Kill tests - **KILL** if existing PMS timestamps and attachments already answer “what is blocked, by whom, and what proves completion?” without parallel work. - **KILL** if teams must duplicate field entry rather than reuse existing messages, exports, or photos. - **KILL** if local process variation prevents one common receipt schema across two operators. - **KILL** if vacancy/rework savings cannot support a price below 10% of verified savings. ### Why it ranks second The pain is frequent and measurable, but incumbent PMS integration and frontline adoption raise execution risk. Discovery must prove that this is a missing evidence layer—not another maintenance board. --- ## 3. ExitBinder — transfer-readiness evidence for small software and digital-service acquisitions ### Problem Small profitable SaaS products, agencies, and digital-service businesses often reach sale with undocumented access, owner-dependent routines, unclear IP custody, brittle vendor relationships, and no current operating evidence. Sellers scramble during diligence; buyers discount uncertainty. ### Target operator / buyer - **Operator:** founder preparing for sale or a fractional COO normalizing operations. - **Economic buyer:** seller initially; search fund, micro-PE buyer, broker, or aggregator later. - **Potential acquirer:** M&A marketplace, broker platform, diligence provider, or portfolio-operations firm. ### Discovery wedge A fixed-scope, human-led transfer-readiness assessment that produces an evidence index—not a valuation and not legal advice. Cover access ownership, recurring operating routines, customer/vendor concentration receipts, IP chain, incident history, and a 90-day transfer plan. ### Evidence required before build 1. Ten buyer/broker interviews and five seller interviews. 2. Three completed or abandoned small-business transactions supplied under confidentiality. 3. A stable set of at least five recurring diligence gaps across all three transactions. 4. Two buyers confirm the resulting evidence index would reduce diligence time or alter a holdback/request list. 5. Two sellers pay for the assessment before listing or LOI. ### Kill tests - **KILL** if the deliverable collapses into generic checklists already supplied by brokers or virtual data rooms. - **KILL** if value depends on legal, tax, valuation, or cybersecurity attestations the studio cannot credibly provide. - **KILL** if sellers will not grant source access before an LOI. - **KILL** if buyers cannot name a concrete diligence decision changed by the evidence index. ### Why it ranks third It fits the studio’s transferability doctrine exactly and may become a proprietary internal operating system. It ranks below the first two because founder access is episodic, trust-heavy, and dangerously close to consulting unless repeated evidence patterns support productization. --- ## Queue decision 1. **Run QuoteLeak discovery first.** It has the clearest economic receipt and fastest manual disconfirmation. 2. Keep **TurnReady** in interview-only discovery until incumbent-system gaps are proven. 3. Use **ExitBinder** initially as an internal transfer-readiness protocol; expose it commercially only after transaction evidence proves a repeatable buyer decision. ## First reversible action Recruit five specialty-contractor controllers/owners for 30-minute interviews. Ask for one redacted closed-job packet only after the interview. Do not design UI, request integrations, or build extraction software until three firms independently clear QuoteLeak’s value threshold.