DRIFTFORGE Partner Audit
Partner interview checklist — script + resume analysis
Goal: run a clean 20-minute Industrial Filter audit and extract signal on system-selling, expansion discipline, and operator grip. Paste a resume below to generate tailored talking points, then use the audit-first backbone as your default run-of-show.
LLM API (resume analysis)
Server-side mode: this page calls /api/analyze. Put provider keys in Cloudflare Pages secrets (not in browser). Pick provider + optional model below. If you use Custom, provide an OpenAI-compatible .../v1/chat/completions URL.
Resume input raw text
Paste a resume, LinkedIn export, or job description. Analysis uses the provider above and stays on this device.
Analysis output
Paste a resume and click Analyze Resume to populate this panel.
Analyzing resume…
Adapt to candidate — defaults below; weave in strengths, red flags, and questions from the analysis panel above.
High-status 20-minute format (audit, not pitch)
First 10 minutes: 2-minute Logic Brief (what) -> 3-minute Expansion Stress-Test (why) -> 5-minute Grip Check (how). Last 10 minutes: scoreboard/risk validation, vertical wedge + tool-fit probe, 2-minute live demo, then hard close at 0:20.
If you pitch a 20-year sales veteran, you become a vendor. If you audit their operating system, you stay in Architect status.
Quick glance · key topics
Use this when you need to scan, land one point, and move immediately to the next.
What — leaky stack -> hardened layer -> gap-fill only.
Why — partner speed must protect 3-day SLA chain.
How — can they enforce behavior change, not sell features?
Risk — forecast discipline + 100% commission reality.
Vertical — wedge market, buyer, and first failure point.
Demo — 2-minute software walk-through: before/after operator state.
Close — inevitable next step, then hard stop at 0:20.
My Vault
Status: local only · non-transmitted
Checklist state, notes, keys, and timer live in this browser only. Nothing here syncs to DRIFTFORGE — a visible boundary: you own the relationship data on your machine; we own the product rails (pillars).
Meeting flow check as you touch
Phase one tabs
Initial Intake Audit
Simple phase one filter: run this before the full gate flow.
Frame — audit system logic, do not pitch features.
Inspect — where does their current process leak first (intake/follow-up/closeout/handoff)?
Constraint — 3-business-day go-live SLA and no custom-build promises.
Decision — proceed to software demo only if they stay in operator language.
Software demo
Two-minute before/after proof, then move to close.
Open — “Two-minute demo: no product theater.”
Show — intake -> documentation -> client-readable proof.
Tie to outcome — fewer disputes, cleaner handoff, faster cash.
Exit — stop at 2:00 and move directly to next step.
Default profile anchors (swap for whoever sits in the chair): 20+ years in sales leadership · national revenue strategist + team culture builder · Director of Local Sales, Terraboost Media (2022-2025): annual revenue from $11.4M to $16.5M (+45%), first CRM install (HubSpot), 80%+ company CRM adoption, 75+ rep system rollout · ANGI/HomeAdvisor: #1 national sales executive, National Sales Team of the Year, back-to-back $24.7M + $26.8M years, enterprise quota ownership and team coaching systems · tools: HubSpot · Salesforce · forecasting/KPI dashboards · territory segmentation · pipeline governance · enterprise negotiations.
Bible anchors: Partners own relationships / DRIFTFORGE owns infrastructure (pillars) · product scope is fixed — no custom builds for clients (scope / custom dev) · gap-fill positioning (never replace/attack competitors) · commission rules are non‑negotiable · Service Level Agreement (SLA) is capacity‑gated · infrastructure is industry agnostic (vertical-agnostic stack): discovery proves the gap, then we deploy a hardened operational layer (hardened layer) — the install adapts when the enforcement logic is there (logic gate) · 100% commission filters for partners who move the needle, not people who babysit a login (comp filter).
Bible anchors: Partners own relationships / DRIFTFORGE owns infrastructure (pillars) · product scope is fixed — no custom builds for clients (scope / custom dev) · gap-fill positioning (never replace/attack competitors) · commission rules are non‑negotiable · Service Level Agreement (SLA) is capacity‑gated · infrastructure is industry agnostic (vertical-agnostic stack): discovery proves the gap, then we deploy a hardened operational layer (hardened layer) — the install adapts when the enforcement logic is there (logic gate) · 100% commission filters for partners who move the needle, not people who babysit a login (comp filter).
Hybrid strip · priority checkpoints
During the call: use this as the scan-order so you don’t lose the spine between bullets and verbatim blocks.
Tap gate
0:00 Logic Brief (what) — leaky stack -> hardened layer -> gap-fill only.
0:02 Expansion Stress-Test (why) — network + infrastructure + 3-day SLA chain test.
0:05 Grip Check (how) — one question, then shut up and inspect operator logic.
0:10 Scoreboard/Risk — forecast discipline + enforcement under pressure.
0:14 Vertical/Tool Fit — wedge, buyer, friction, and no-build baseline.
0:16 Demo — 2-minute product walk-through tied to operator pain.
0:18 Close — speed + certainty + inevitable next step.
Control — acknowledge + 20-min clock + infrastructure logic.
0:20 Exit — hard stop; Thu 5pm; one-message rule.
Vertical probe 1: Which vertical do you already have distribution in, and which buyer role signs?
Vertical probe 2: What breaks first in that market today: intake, follow-up, closeout, or handoff?
Tool-fit probe: If we built one secondary tool for that vertical, what job must it remove from day one?
No-build check: What can we solve with protocol + language only before any custom build?
0:00 — Logic Brief (the what)
Set architect frame: audit the system, do not pitch software.
Verify proof stack — 20+ years national sales leadership · Terraboost revenue lift (+45%) · first HubSpot CRM rollout for 75+ users · ANGI/HomeAdvisor #1 performance with multi-year over-quota enterprise output.
Verify stack literacy — HubSpot + Salesforce architecture, KPI enforcement, weekly forecast discipline, territory segmentation, coaching cadence, and enterprise negotiation control.
Set evaluation frame — “I’m not here to be impressed — I’m testing fit + coachability inside our system.”
Declare the constraint: 72‑hour delivery timeline (fulfillment cycle) on high-value accounts (Whale accounts) (speed + precision required).
Hit the Four Pillars: partners own relationships / DRIFTFORGE owns infrastructure (pillars) · software fulfills / partner sells (pillars) · partners are operators not employees (partner language) · partner isolation is by design (isolation).
Scope lock (scope) — product scope is fixed, so we don’t promise custom builds (custom dev); partners can’t either.
Define what you’re measuring: can they sell a protocol under rules (not run a vanity brand campaign), respect capacity + language standards, and stay coachable.
Ask the pivot question: why Founding Partner here vs another in-house Director/CMO path or agency portfolio (listen for leverage, recurring book, system — not “more creative control” alone).
Industry-agnostic spine (vertical-agnostic stack): same protocol backbone across trades; you’re not selling a single vertical headline — you’re proving whether their world has real gap logic worth a hardened install (hardened layer).
Prompts before the verbatim Say block
Bridge in one breath — proof you read them → why this seat exists → clock + fulfillment reality (fulfillment cycle); don’t sandwich in small talk.
Land pillars + scope — relationship ownership vs infrastructure (pillars) first; then scope lock (no custom builds) short and flat.
Use silence — after the two non‑negotiables, half-beat pause; let them lean in.
Single pivot — the closing question is the hook; resist stacking extra asks here.
Paraphrase OK — keep sequence: praise signal → constraint → rules → why here.
Say:
I will keep this brief because we both have a launch to manage. Most trade software is a leaky bucket: it handles billing, but loses the documentation handshake in the field. DRIFTFORGE is the hardened layer that seals those gaps with digital guardrails.
We do not replace the stack; we reinforce it (gap-fill). Partners own relationships and DRIFTFORGE owns infrastructure (pillars). Scope is fixed: no custom builds promised in the field (scope).
I am not here to pitch you. I am here to audit whether you can sell a disciplined system under operator constraints.
0:02 — Expansion stress-test (the why)
Test whether they can scale inside SLA and protect fulfillment chain discipline.
Gap preset · vertical wallpaper
Industry-agnostic spine — swap scenario wallpaper for screen-share. Default is broad field/trades; pick a vertical for a sharper stress test.
Reframe the sale: “We don’t sell software — we install a documentation protocol (protocol).”
Run the hard objection: “My crew will never use digital — they’re paper / old-system people.”
Force identity framing: “You’re a professional shop / you run a standard, not preferences.”
Listen for enforcement mechanics: consequences, standard operating rhythm (cadence), manager inspection, onboarding/training cadence (cadence).
Listen for language quality: do they talk outcomes (fewer disputes, cleaner books, faster cash) or features (“buttons, screens”)?
Green tell: they make compliance the cost of entry without turning it into a branding exercise.
Inject the product suite (Bible): NoteRelay (NoteRelay) = client communication clarity; CloseDoc (CloseDoc) = closeout docs + photo trail; Gap Matrix (Gap Matrix) = discovery framework; we plug gaps without replacement (gap-fill).
Industry-agnostic install (vertical-agnostic stack): if discovery shows real friction — slow intake, leaking follow-up, closeout slippage (workflow gaps) — we can deploy the hardened layer there (hardened layer); no replacement story, no “rip and replace.”
Example · legacy stack vs floor speed — e.g. heavy dealer / DMS or enterprise ERP bias toward accounting (compliance load) while intake + follow-up leak on the floor (floor friction): systems gap, not a campaign fix; we don’t rip the core system (gap-fill) — we harden documentation + client-readable proof where discovery proves the hole.
Prompts before the verbatim Ask block
Optional one-liner — in your voice: “different buyer than ad metrics — we’re selling protocol on a floor.” Then dive into the block.
Don’t rescue — if they stall, repeat the scenario once calmly; no leading the witness.
Run the follow-up — weekly inspection, 30-day tolerance, consequence — even if they nailed the first beat.
Feature detour — “buttons and training later” is a yellow signal; nudge back to identity + enforcement.
Ask:
You have the network and I have the infrastructure. I only look for partners who can sell disciplined systems, not "easy software." My go-live SLA is 3 business days because the logic is standardized.
If a partner cannot move at that speed, they break my fulfillment chain. How do you expand without breaking my chain?
Follow-up: if the owner pushes back with "my team will not adopt this," what exact enforcement standard do you set in week one?
Listen for: chain logic + enforcement mechanics + no feature detour.
0:05 — Grip check (the how)
One high-level question. Stop talking. Inspect operator grip.
Demand their actual scoreboard: 3–5 weekly metrics they ran as Director (e.g., Customer Acquisition Cost (CAC) / Cost Per Lead (CPL), conversion rate (CVR), pipeline quality (pipeline hygiene), revenue pacing, channel attribution).
Test forecasting integrity: how they prevent sandbagging / optimism and how they define “real pipeline.”
Test system enforcement: what happens when a top performer (sales or channel owner) refuses Customer Relationship Management updates (CRM hygiene) or Key Performance Indicators reporting (KPI reporting).
Ask for exception logic: when do they break the rule (if ever) and how do they prevent “exception becoming policy.”
Green tell: calm, specific standards + consequences; no hero worship of “the creative” or one channel that won’t follow process.
Drop the comp constraints (Bible): Monthly Recurring Revenue (MRR) pays on active clients only (MRR) · setup commission held 31 days from go-live (31‑day hold) · payout is the 15th for clients active as of the 1st (payout cycle) · enterprise deals need a signed Deal Memo before pricing is shown (Deal Memo).
Prompts before the verbatim Ask block
Frame the seat — “partner scoreboard” and fulfillment handoff before you read the dashboard question.
Definitions over drama — push what “pipeline” and “qualified” mean before more tactics.
Forecast miss — make them rank: bad inputs vs mushy definitions vs weak enforcement.
Star player exception — if they wax poetic about a rainmaker, lock how the rule still applies.
Ask:
When you walk into a shop where the owner is drowning in paperwork and his techs are lazy with their notes, how do you explain that DRIFTFORGE is not "more work," but the only way they scale without breaking?
Follow-up: where is your first point of leverage in that room - identity, economics, or enforcement?
Listen for: operator language + behavior change design + system-selling under friction.
0:10 — Scoreboard + founder risk validation
Validate forecast discipline and willingness to carry performance-only accountability.
Make the contrast explicit: W-2/retainer stability + marketing budget authority vs 100% commission (performance-only), early-stage, no safety net.
Force a mechanism: what can they build here that they can’t as CMO/Director or running paid media for clients?
Listen for founder logic: recurring book (Monthly Recurring Revenue — MRR), leverage, compounding, ownership — not “I want a side project.”
Watch for avoidance: if they won’t name trade-offs (risk, volatility, timing), yellow flag.
Green tell: they can articulate why the risk is rational and how they operate with no campaign dopamine for a week.
Prompts before the verbatim Ask block
State risk once — 100% commission / no net; don’t negotiate the model in this gate.
Listen for specifics — cash buffer, runway math, ego vs leverage; vague “I’m a grinder” = dig.
Dead week is the test — day two / day five rhythm reveals dependency on campaign wins.
Stay warm, stay binary — empathy without selling them the seat.
Ask:
You’ve operated at Director level with real budget, channels, and reporting — the kind of role people stay in for stability and prestige. This seat is 100% commission, early-stage, no safety net. It’s that way on purpose: we want partners who can move revenue and install discipline in the field — not people looking to babysit a login and call it work (comp filter).
Why take founder-level risk here instead of the next Director/CMO seat or staying inside a brand you already know?
Follow-up: if you have a dead week — no pipeline movement, no campaign wins to hide behind — what does your operating rhythm look like on day two and day five?
0:14 — Vertical wedge + tool-fit check
Map wedge market, buyer path, and whether a secondary tool is truly justified.
Force specificity: one enterprise program, named roles (Economic Buyer (EB), Champion (Champion), Blocker (Blocker)).
Find the stall: where did it slow (legal, ops, procurement, implementation fear, politics).
Extract the leverage move: what did they do that changed the deal state (sequence, memo, meeting reset, constraint, proof asset).
Assess control points: how they kept the next step owned and time-bound (next step).
Green tell: they speak in stakeholder map + sequence, not campaign highlights alone.
Industry story without a vertical cage: they can name pain in their sector (e.g. platform bloat vs floor speed) but translate it into gap + protocol language — same spine as any other trade (vertical-agnostic stack).
Verify relationship depth — after the account story: did they surface names, roles, and veto paths — or only industry gloss? Log one tap in the audit row below (optional; say it once aloud so it doesn’t feel like a tribunal).
Prompts before the verbatim Ask block
Their pick — let them name the account; only narrow if they freeze.
Stall vs person — separate “where it slowed” from “who made it move.”
Veto without theatrics — follow-up is about neutralizing risk without over-promising.
If they filibuster — “Who had veto, in one sentence?”
Ask:
Which vertical do you wedge first in your first 90 days, and who is the economic buyer in that segment?
Follow-up: what breaks first there - intake, follow-up, closeout proof, or handoff - and what can we solve with protocol before asking for any secondary build?
Listen for: precise vertical logic, buyer clarity, and no-build-first discipline.
Audit · relationship depth
Rolodex / network signal — after they tell the account story, tap the box that matches how specific they got.
0:16 — Demo window (2 minutes max)
Show only enough product to reinforce the audit logic.
Set scope: “Two-minute demo only — before/after operator state, not feature tour.”
Show sequence: intake signal -> field documentation -> client-readable closeout proof.
Tie to economics: fewer disputes, faster approval, tighter cash timing.
Hold line: no custom asks in-demo; park requests for post-evaluation.
Prompts before the demo
Open with operator pain — “this is where paper leaks margin.”
Narrate outcomes — what changed operationally, not where to click.
Stop at 2:00 — leave curiosity, move to close test.
Say:
Quick demo window — two minutes, no product theater. I’ll show one before/after path: how a messy paper handoff becomes operator-standard documentation with client-readable proof, without replacing your current stack.
0:18 — Close test (live sell)
Make them sell speed + certainty, not a funnel metaphor or deck speak.
Force the frame: “30‑second audit” (speed + relief), not a product tour.
Watch their opener: owner pain (paper → disputes → slow cash) vs “we have an app” or ad jargon.
Listen for identity: “this is how real shops document work” / “this is the standard now.”
Listen for close mechanics: next step (next step), urgency, and a clean one-sentence value claim.
Red flag: they keep talking after the point is made (can’t be concise under a clock).
Require the Bible positioning line: never attack competitors; we complement them (gap-fill): “They handle ops. We handle closeout + client comms. We don’t replace anything.” (positioning).
Prompts before the verbatim Say block
Play the owner flat — tired, skeptical, not a coach; short answers from you.
Timer discipline — if they run past value, tap the clock mentally; you want one sharp pass.
Gap-fill only — if they attack the stack, reset constraint once, then hold.
Demand the close — one sentence next step you’d actually take; “optional” loses the test.
Bonus line optional — industry-agnostic line only if they nailed simplicity first.
Say:
You understand sales systems and leadership mechanics — HubSpot, Salesforce, forecasting discipline, KPI coaching, and enterprise account control. Your job right now: sell me the speed of a 30-second audit as if I’m an owner-operator drowning in paper, disputes, and slow cash — pick any trade mentally; keep it plain English, owner-to-owner. No funnel theory.
Constraint: you can’t attack or replace their current platform — you can only gap-fill (positioning).
Reality check you can verbalize if useful: our infrastructure is industry agnostic (vertical-agnostic stack) — we’re not wed to one vertical myth; we harden where the gap logic shows up (hardened layer).
Bonus: end with a one-sentence next step that feels inevitable — not optional.
Any time — if they try to take over
Keep control without friction.
Use the line once: acknowledge + clock + “infrastructure logic” + move on.
Assess compliance speed: instant adjustment (Green) vs negotiation (Yellow) vs pushback (Red).
Watch dominance behavior: do they keep trying to reframe you, or accept your frame and perform inside it?
Prompts before the verbatim line
Deploy once per derail — acknowledge → clock → infrastructure logic → forward motion.
Tone — bored bulletproof, not irritated; no stack of excuses after this.
No negotiation — don’t debate whether 20 minutes is “enough.”
I hear you — but we’re on a 20-minute clock and I need to stay in the infrastructure logic. Let’s keep moving. If there’s time at the end, we’ll circle back.
0:20 — Hard stop (exit)
End exactly at 0:20 — even mid-sentence.
Hard stop on time: do not apologize, do not negotiate (boundary is the test).
Status language: “audit complete” + “processing candidates” (you’re not chasing).
Specific promise: Activation link by Thursday 5 PM if logic clears (hold the line).
Post-exit discipline: if Green, no reach-out for 24 hours; let silence do work.
Prompts before the verbatim close
Swap [Name] — say their actual name; no placeholder on the call.
Cold facts — two short paragraphs; resist “how’d I do?” energy from your side.
Thursday promise — say the time once, same wording as script, then stop.
Follow-up boundary — one message rule is load-bearing; don’t soften it.
[Name], the audit is complete. I’m processing additional candidates today. If the logic clears, you’ll receive the Partner Activation link by Thursday at 5 PM. Appreciate your time.
If you have follow-ups, send them in one message — I’m staying inside the evaluation sequence.
Phase 2 founder strategy session — run only after a Green pass from Phase 1.
Founder strategy session phase 2 · 25 minutes
Phase 2 hybrid strip · founder decisions
Goal: decide market wedge, operator profile, and whether a secondary vertical tool is justified.
Phase 2 flow
Open — confirm this is strategy, not another audition.
Vertical fit — isolate the market where they can move fastest with existing trust.
Tool thesis — prove if secondary tool demand is real or a symptom of weak install.
Decision — lock next experiment, owner, and deadline.
Phase 2 / 0:00 — Founder frame
Set this as a strategy build session, not a personality screen.
Say:
You passed Phase 1. This session is founder strategy: market wedge, operating model, and where a secondary tool is actually justified. I care about what ships and what compounds, not pitch polish.
Phase 2 / 0:10 — Vertical reality map
Identify the one vertical where they have both access and pain clarity.
Access — ask where they already have decision-maker trust.
Pain unit — make them name the exact recurring failure point.
Economics — tie pain to time-to-cash, dispute cost, or margin bleed.
Ask:
Which vertical should we wedge first, and why that one now?
Who is the economic buyer there, and who usually blocks implementation?
What breaks first today in that market: intake, follow-up, closeout quality, or handoff?
If we fixed one of those in 30 days, what KPI would move first?
Phase 2 / 0:17 — Secondary tool thesis
Separate true tool demand from process and language enforcement problems.
No-build baseline first — require what can be solved by protocol with current stack.
Build trigger — define one repeatable blocker that justifies product work.
Constraint — no custom one-off for one client logo.
Ask:
Before we build anything, what can we fix with process discipline and tighter field language inside the current stack?
Now the hard call: if we built a secondary tool for your vertical, what exact job must it remove on day one?
What would make you say "do not build this yet" even if prospects keep asking for it?
Phase 2 / 0:24 — Decision close
Leave with one market test, one owner, one date.
Say:
Good. We are locking one vertical wedge, one 30-day proof test, and one owner. If signal is clean, we expand; if not, we do not add tool surface area. I want your written test plan by tomorrow, 5 PM.
Adapt to candidate — scoring rubric is fixed; your one-line reason should reference their specific signals from today.
Post-call 5 minutes
Score it immediately. One word + one sentence.
If Green — do not reach out for 24 hours
Silence is leverage. Send activation link Thursday by 5 PM as promised — not before.
If Yellow — name the gap precisely
Mindset vs skill vs risk tolerance. Decide if a second audit is worth it.
If Red — close the file
No follow-up.