Operator partnership · done-with-you tier

Skip the build. Hire the team that wrote the dossier.

Essay: Read the math on when this tier makes sense, what each phase costs, and the three failure modes

If you'd rather not assemble a team, configure the stack, write the outreach, and run the first 50 sales conversations yourself, this is the tier where we do that with you. The Factory has shipped 822 idea kits and graduated one to its own domain (intakecounsel.com). The team behind it ships real revenue against real customers across LinkedIn automation (Sales Connector, 165 paying tenants), Pi-based hardware (ProxyBox.us, shipping in boxes), voice AI, and field-service software.

Phase A fixed at $2,500 Phase B + C scoped per engagement, $15K - $45K typical You own the code, the brand, and the customer relationships

Three phases. You can stop after any phase.

Most engagements run Phase A then a single combined Phase B+C. A few stop after Phase A because the validation work surfaces a clearer offer than the original dossier. That's the right outcome.

Phase A · week 1

Scope confirmation

$2,500

Walk the dossier with you, validate ICP against your network, lock the brand and pricing, write the v1 launch checklist.

  • 2 paid 90-min strategy sessions
  • Reaffirm ICP with 5 cold-call validations
  • Brand and pricing locked
  • Phase B and C scope and quote delivered
Phase B · weeks 2 to 4

Build to MVP

$10K - $25K

Build the working version of the product: auth, billing, the single workflow that solves the named pain, deployed to your domain.

  • Code starter customized to your stack
  • Domain, hosting, SSL, billing wired
  • Onboarding flow tested end-to-end
  • Pilot-ready by week 4
Phase C · weeks 5 to 8

Launch outreach

$5K - $20K

Run the first 50 outbound conversations. Train you on the operating cadence. Hand back a working pipeline.

  • 50 LinkedIn / email touches with handoff playbook
  • 5 to 15 paid pilots aimed for
  • Operating cadence document
  • Hand-off + next-30-day plan

Why the team behind this can actually ship.

The proof you should care about is what we have already shipped to real customers, not what we promise to ship for you.

Catalog graduation

Counsel AI shipped to its own domain

Started in this catalog as the lawfirm-ai dossier. Six weeks later it is at intakecounsel.com with standalone marketing and an active launch. The case study is at /factory/playbooks/counsel-anatomy/.

SaaS at scale

Sales Connector + InfoNet

LinkedIn automation platform with 165 paying tenants and 153 white-label resellers. Companion site at infonet.co for self-serve buyers. Production stack: Apache, PHP, Node, MySQL 8, cPanel, Caddy.

Hardware product

ProxyBox.us shipping in boxes

Pi-based residential proxy hardware with BLE-over-iPhone onboarding, Stripe billing, fleet of customer Pis on OTA firmware. Real product in real boxes, not just a deck.

Autonomous studio infra

The Factory itself

100+ cron jobs, 68 monitored endpoints, 0-em-dash invariant durably enforced. Bulk LLM generation pipeline that produced 60 operator-voice product pages in 45 minutes. The Factory eats its own dog food.

The Factory was not bolted onto a pre-existing template-driven SaaS. It was built from scratch in six weeks while the operator was also running 5 other shipping products. If the question is "can these people actually ship", the answer is yes, demonstrably, at scale.

What's in scope vs. out of scope

  • In scopeBuilding the product, configuring billing, writing landing/pricing/FAQ pages, deploying to your domain, drafting the outreach pack, running the first 50 outbound touches with you on the cc line, training your team on the operating cadence.
  • In scopeBrand identity (palette, typography, voice), copy library for first 90 days, founder bio if you want one, audio pitch via fish.audio, hero UI screenshots.
  • In scopeFirst-party integrations to your CRM and email + LinkedIn outreach systems. We've built against HubSpot, Pipedrive, ULINC, custom-cPanel, and Postgres at scale.
  • Out of scopeLong-term operations. We hand back at week 8 unless you want to extend on month-to-month at $5K/mo retainer.
  • Out of scopeMobile app development unless explicitly scoped. iOS work adds 4-6 weeks and is a separate engagement.
  • Out of scopeRegulated verticals (healthcare PHI, banking-grade compliance, regulated finance). We can refer.

Examples worth a Phase A conversation

These are the highest-Adoptability ideas from the catalog right now. They tend to convert into operator-partnership engagements because the buyer is named, the distribution path is proven, and the build is bounded enough to ship in 6-8 weeks.

See all 627 ideas in the catalog →

Questions operators actually ask before signing.

These come up in almost every Phase A conversation. The answers are the honest ones we give in person.

What if the dossier turns out to be wrong about my market?

That is what Phase A is for. We spend the first week running cold-call validations against your network and your ICP, not ours. If five of those calls land badly, the right move is usually to refactor the offer before committing to Phase B, not to start building. Phase A is a real $2,500 not a try-before-you-buy, because the validation work is the work. About one in five Phase A engagements end with "the original idea is wrong, here is the adjacent idea your network actually wants." That counts as a successful Phase A.

What is the timeline from "yes" to "live with first customers"?

For a typical Phase A + B + C combined engagement: week 1 validation, weeks 2-4 build to MVP, weeks 5-8 launch outreach. So pilot customers in week 5 to 6, real revenue in week 8 to 12 if the offer lands. If the validation in Phase A surfaces a different shape of product, add 2 to 4 weeks. We do not chase timelines that compress below 6 weeks total because the resulting work is brittle.

Who owns the code, the brand, and the customers?

You do, fully. Code in your GitHub org, brand on your domain, billing to your Stripe, customer relationships in your CRM. We hand off everything at week 8. The only ongoing tie is if you opt into a $5K/month retainer for continued operations support, which most engagements do not take. We are not in the equity-skimming business.

What happens if the engagement does not work?

Define "does not work" carefully. If Phase A surfaces that the idea is wrong, that is a successful Phase A (you saved a quarter). If Phase B ships an MVP that does not convert, that is a Phase B failure, typically because the ICP was wider than Phase A validated. We do not refund Phase B if the code shipped on spec, but we will run a structured post-mortem and refund Phase C if we have not started the outreach yet. We have never had a Phase C fail to surface at least one paying pilot, but we name the risk honestly because that is the engagement worth running.

Why is the team you, mostly?

Because the alternative for an operator partnership at this price band is a 4-person agency with a project manager layer and a slow Slack channel. Operator partnerships work best when one person owns the engagement end to end. For specialized work (iOS, Remotion video, voice AI), the team expands. For most engagements, you talk to Wes from Phase A to handoff. That is a feature, not a constraint.

Ready to talk?

Email Wes with the idea you're considering and the audience you'd want to sell it to. The first reply usually comes within a day.

Email wes@wishdeal.com

Honest read: an operator engagement is a head start, not a guarantee. We can build the product and run the first 50 conversations. Whether the next 500 conversations turn into a real business depends on what those first 50 reveal and what you do next. We've shipped products that became real businesses and shipped products that became cautionary tales. Our honest page is here.