The platform doesn't create opportunity — it captures the opportunity already in WyoHouses' and Bighorn's pipelines that's currently slipping. Here's what that looks like on a monthly basis.
The math on delay: A 60-day decision window — from today to contract signature — means Workflow 1 doesn't enter production until Week 14 and Workflow 2 doesn't go live until Week 18. That's four additional months of manually-ranked deal flow and an investor list that ages every week it goes un-contacted. Conference lists have a shelf life. The NAPE Tier 1 contacts from February 2026 are at peak relevance now.
Early commitment carries structural weight. What's documented below is separate from — and in addition to — the line items in the deal. These terms exist because Bighorn is being asked to move first — and first movers deserve something the second wave doesn't get.
The deployment fee, monthly retainer, and 3% performance share are locked for 18 months from production launch. Retail SKUs and pricing for new customers may publish during that period; Bighorn's terms do not change until the locked window closes — at which point any rate adjustment is mutually negotiated, not unilaterally imposed.
Bighorn's voice, buy-box criteria, investor language, objection patterns, and operational rhythm directly shape how Workflow 1 and Workflow 2 behave. That input is captured during build and continues through the calibration period. Feature priorities surfaced by Bighorn — Recon enhancements, new bird-dog source types, IR workflow refinements — go to the front of the roadmap when they align with platform direction.
No ticketing system. No support tier escalation. Casey, Ashley, and Bighorn's team have direct line access to Ainsworth Group's principal for urgent issues, workflow changes, and on-demand requests. Standing weekly sync available, optional, agenda set by Bighorn — use it or skip it.
Several conversations sit outside this proposal by design — they involve principals, equity, distribution, and longer-horizon questions that don't belong in a Phase 1 customer agreement:
Every operator, every workflow, every data pipeline in Phase 1 was validated against real conditions before a formal scope was written. The infrastructure decisions along the way were deliberate staging choices — not permanent commitments. Each one had a clear thesis, a clear objective, and a clear outcome. Here's the sequence.
Conference rooms full of qualified operators and capital don't automatically produce pipeline. Names on a badge without contact infrastructure are worthless — regardless of relationship quality.
Determine whether an AI-native data pipeline could convert name-only conference lists into verified, callable contacts at speed — without manual research or third-party researchers.
OpenClaw was deployed inside the operation to run the first live test against the NAPE Houston attendee list.
Before committing to permanent infrastructure, the data pipeline needed live validation. A disposable staging environment is the correct first move — fast to deploy, cheap to iterate, and replaceable once the underlying question is answered.
Stand up a VPS on Hostinger, deploy OpenClaw, and run the NAPE list through the full pipeline — skip tracing, contact enrichment, and actionable output — without manual intervention.
The pipeline worked. The NAPE list became callable. The staging environment served its purpose.
Scale introduces friction that isn't visible at smaller volumes. SquadUp generated over 1,000 unique impressions — a meaningfully larger dataset that would either confirm the NAPE findings or expose new failure modes.
Run the same pipeline validation against the SquadUp roster. But look beyond data quality — interrogate the operational patterns that determine whether qualified contacts actually convert to meetings.
Two systemic gaps emerged: high schedule rates paired with low attendance — a follow-through problem, not a sourcing problem — and clear inefficiencies in how birddogs were surfacing Revive deals. These were workflow failures, not data failures. They defined exactly what the operator layer needed to solve.
Two separately validated systems — the Ainsworth Group production stack on Cloudflare and the OpenClaw pipeline running on Hostinger — should be composable. Bridging them would demonstrate the combined capability without a full production build.
Integrate Ainsworth Group's Cloudflare-hosted codebase into the OpenClaw staging environment and run a live MVP against Bighorn's actual workflow problems — not a demo against synthetic data.
The MVP performed as modeled. Both systems composed cleanly. The combined capability was demonstrated against real conditions.
Thesis. A staging environment that has answered its questions should be retired. Continuing to operate WyoHouses' live deal flow and Bighorn's investor outreach on a disposable VPS introduces risk with no corresponding upside.
Decision. Migrate off Hostinger. Deploy a dedicated, production-grade workspace on Ainsworth Group's Cloudflare infrastructure. The operators validated in staging become a managed operating system running against WyoHouses' deal pipeline and Bighorn's capital raise.
Why the Hostinger spend is not a sunk cost. Every dollar spent in staging bought certainty. Phase 1 is not a speculative build — it is a proven system being deployed at scale, against a problem set that has already been defined and validated in production conditions.
Every step above reduced uncertainty. NAPE tested the data thesis. The VPS staging environment tested the pipeline. SquadUp defined the workflow problems. The MVP bridge proved composability. The Hostinger infrastructure served its purpose and is now complete.
Phase 1 is not a bet on untested technology.
It is a production deployment of a system that has already been run against real data, real operators, and real workflow constraints.
Workflow 1 runs for WyoHouses — deal flow, the Revive Method pipeline, birddog submissions, and ranked acquisition opportunities. Workflow 2 runs for Bighorn Capital Fund — investor qualification, capital raise, and IR calendar. Each one is a chain of operators that runs in order — input, agent, agent, output. One management band sits above both lanes. One Cloudflare floor runs underneath. What you see in the diagram is exactly what runs in production.
AI operators execute defined logic at speed and scale. That is their advantage. It is also their constraint.
They run exactly what they were configured to run — and they keep running it until a human changes the configuration. Markets shift. Investor cohorts respond differently over time. A comp set that was accurate in Q1 misfires in Q3. A skip-trace pipeline tuned for one list format silently fails against a new one. The operators do not detect these conditions. They do not self-correct.
Ainsworth Group reviews outputs weekly, identifies where operational logic has drifted from market reality, and recalibrates before performance degrades. That is the work the retainer funds.
None of these failures surface as error messages. They surface as gradually declining output — fewer ranked deals, lower meeting attendance, softer qualification rates. By the time the pattern is visible, weeks of throughput have been lost.
A qualification prompt converting at 18% in Month 1 will reach 11% by Month 3 without active tuning against live call transcripts.
A skip-trace pipeline calibrated to one list format silently misfires when the next format arrives.
An underwriting model trained on a prior comp set starts producing inaccurate exit scores as the market moves.
The management layer exists to catch drift before it compounds.
The Cloudflare layer at the base of the diagram marks a specific operational transition. The Hostinger VPS was the right choice for a staging environment — fast to deploy, low overhead, purpose-built for a question that needed answering. That question has been answered. The staging environment is complete.
Phase 1 deploys a dedicated workspace on Ainsworth Group's Cloudflare infrastructure:
The VPS goes dark. The production system goes live.
The thesis build surfaced one constraint that appears in every test. Casey already has the inputs — investor lists, conference pipelines, birddog networks, a defined buy-box, an operational cadence. The throughput ceiling isn't a strategy problem. It's a human bandwidth problem. One principal cannot simultaneously work every lead, underwrite every deal, follow up on every warm contact, and run a capital raise. The platform exists to remove that ceiling.
Phase 1 deploys the Ainsworth Group platform against two highest-leverage workflows — Workflow 1 for WyoHouses (deal sourcing, the Revive Method pipeline) first, Workflow 2 for Bighorn (capital raise, IR) second. The ordering reflects how the business actually runs today: the deal pipeline is producing now, so we instrument against existing volume immediately. The capital raise is the growth motion built on top of that foundation.
Casey has been running an Ainsworth Group operator in production since Q1 2026 — the Daily Brief. Confirmations the night before. Auto-reschedule with three options if unconfirmed thirty minutes prior. 7am briefing every morning. Phase 1 is not the first time the platform runs against Casey's operation. It's the first time it runs against WyoHouses' deal pipeline and Bighorn's capital raise.
These workflows are independent. They serve different audiences, operate different operators, and produce different outputs. They share a platform layer and a single management contract — but WF1 producing does not depend on WF2 launching, and vice versa.
Both workflows share a platform layer underneath: Recon's intelligence APIs, the dashboards, the observability, and the Daily Brief — already running daily for the team.
WF1 and WF2 don't reach across each other. They reach down, into the same shared infrastructure. That's how a single management contract runs both without coupling them.
The two workflows compound on two different timescales — one inside every deal, one across every quarter.
Every operator reads and writes to the same deal record. No handoffs. No re-entry. No coordination tax. Scout's distress signals shape Recon's underwriting. Recon's exit scoring shapes Envoy's negotiation. The system gets smarter with every deal it touches.
Closed deals build a track record. The track record becomes the most credible asset Workflow 2 carries into investor conversations. Committed capital funds the next acquisition cycle. Deal volume increases. The track record strengthens further. WF1 and WF2 don't need each other to launch — but once both are running, each one raises the ceiling of the other.
Scout monitors distress signals, ownership transitions, and off-market indicators across WyoHouses' target geographies — automatically. Birddog submissions, Revive Method leads, and MLS distress signals all enter the same queue with a complete intelligence packet attached, not a raw address. Casey's acquisition team reviews ranked opportunities, not raw submissions.
Recon enriches every WyoHouses property with the inputs the Revive Method underwriting actually uses — comps, ARV, rehab signal, neighborhood velocity, and exit-strategy fit. The output is an underwriting brief, not a property card. The team reviews recommendations, not raw data.
WyoHouses doesn't run one buy-box — it runs several, segmented by capital source, geography, and exit. Scout's matching layer routes each enriched property to the right desk: in-house Revive acquisition, lender pipeline, wholesale opportunity, or referral partner. Nothing sits in a generic queue.
Upload any list — NAPE attendees, SquadUp roster, LinkedIn exports, purchased leads. Envoy calls each prospect, confirms accreditation, gauges deployment intent and timing, and books qualified meetings on Bighorn's Investor Relations team's calendar — only for accredited investors with a real intent to deploy capital. Cold names that don't qualify never reach IR.
Past investors who said "not right now" are the warmest leads in any pipeline. Envoy calls them with fund updates, new deal highlights, and distribution performance — giving them a reason to re-commit without a sales push.
After a successful investment — or even after a good conversation — Envoy follows up asking for introductions. Warm referrals convert at 5–10× the rate of cold leads. This mode mines them systematically without requiring Casey to make the ask.
A single live console — not a monthly report. WyoHouses pipeline health, Bighorn raise progress, agent performance, deal queue, and operator anomalies, all in one place. Observational AI runs in the background flagging drift, missed handoffs, and conversion-rate changes before they become this week's problem.
Workflow 1 launches first — WyoHouses deal flow. Recon, Scout, and the buy-box matching layer run on real Revive Method properties, real birddog submissions, real comps from day one. The team evaluates output during a 30-day calibration window.
Workflow 2 activates second — Bighorn capital raise. Once Workflow 1 is calibrated and the IR team has capacity to absorb qualified investor meetings, Envoy begins working the NAPE list, SquadUp roster, and CRM contacts.
Neither workflow is speculative. Each runs against a problem that has already been validated in the field.
The first 30 days post-launch for each engine are calibration — operators tuning to Bighorn's voice, buy-box, and investor language against real activity. The proof window opens once both engines are live and instrumented. Phase 2 conversations begin only after that window produces.
Phase 1 operates on uploaded lists, exported rosters, and the platform's native pipeline view. Direct integration with Bighorn's existing CRM is optional and not included in this scope — it adds material engineering surface and is best handled as a separate engagement once Phase 1 is producing.
That said, here's what a CRM integration would unlock when Bighorn wants it: every Envoy call writes back to the contact record automatically, every Recon enrichment populates the property record, lead status changes flow bidirectionally, and the IR team works inside the CRM they already use rather than a parallel console. Estimated separately as a follow-on build when Phase 1 is producing and the CRM target is selected.
This is not a CRM. This is not a dashboard.
This is the execution layer for WyoHouses and Bighorn.
Once one operator runs on Casey's data, every subsequent operator inherits that context. A point tool can replicate a single function. It cannot replicate six months of deal-record intelligence that compounds across every phase of the acquisition cycle.
Average mid-market investment for a custom-built AI agent system in 2026 falls between $45K and $120K. Integrated agentic systems with multi-agent orchestration: $50K–$150K. Monthly retainers: $2,500–$15,000.
For a production agent serving real users: $3,200–$13,000 per month covering LLM API costs, infrastructure, monitoring, monthly tuning, and security maintenance. Integration engineering and QA/safety testing alone account for 40–60% of total build cost.
Multi-step reasoning agents with tool integration: $20K–$80K. Full multi-agent systems with custom RAG pipelines, enterprise integrations, and safety evaluations: $100K–$500K+. Maintenance budgeted at 15–20% of build cost annually.
Most SMEs invest $30K–$100K upfront for a custom agent tailored to their workflows. Enterprise deployments with custom training and dedicated support: 10–50× more than basic SaaS subscriptions. Hidden integration costs: 20–40% on top of platform fee.
This scope sits squarely in the upper-mid agentic range. Two distinct workflows sharing a platform layer. Voice + telephony + skip tracing + real-time intelligence APIs + 506(c) compliance handling. Equivalent agency-built scope at Q1 2026 market rates would land at $100K–$200K for the build and $8K–$13K per month for managed operations.
Sources: Agix Technologies (Q1 2026), Azilen Technologies (Q1 2026), Groovy Web (Feb 2026), The Crunch (Q1 2026). Benchmarks reflect U.S. agency rates for comparable agentic AI scope. Anchor partner pricing reflects early commitment, co-development access, and named reference rights — documented in the next section.
Conservative, base, and upside scenarios — modeled on volume Casey already has the inputs to support across both WyoHouses and Bighorn. No synthetic assumptions.
| Metric | Conservative | Base | Upside |
|---|---|---|---|
| Properties enriched / month | 200 | 500 | 1,000 |
| Buy-box matched deals / month | 15 | 40 | 80 |
| Submission-ready deals / month | 5 | 12 | 25 |
| Incremental closed acquisitions / quarter | 2 | 5 | 10 |
| Avg net acquisition profit (flip or hold) | $35K | $45K | $55K |
| Annual incremental P&L contribution | $280K | $900K | $2.2M |
| Metric | Conservative | Base | Upside |
|---|---|---|---|
| Prospects called / month | 250 | 500 | 1,000 |
| Qualified leads / month | 25 | 75 | 150 |
| Meetings booked with IR / month | 8 | 25 | 50 |
| Investors committed / month | 2 | 5 | 10 |
| Avg check size | $25K | $50K | $100K |
| Annualized capital raised | $600K | $3.0M | $12.0M |
WF1 enriches 500+ properties in its first month. WF2 makes 500+ calls. No ramp period beyond 30-day calibration. No sick days. No missed follow-ups.
Three line items. No tier matrix, no usage credits, no add-ons.
|
Deployment Fee
One-time. Covers all build work for Workflow 1 and Workflow 2 — Recon's underwriting layer, Scout's matching logic, Envoy voice + telephony stack, dashboards, observability, integration QA, and team onboarding.
|
$35,000
Invoiced at kickoff
|
|
Monthly Retainer
Covers Ainsworth Group's time and managed operations across both workflows — platform infrastructure, prompt tuning, model upgrades, dashboards, observational AI, daily uptime monitoring, weekly performance review, monthly model refresh, and on-demand support. Hosting, LLM inference, voice and telephony, enrichment APIs, and skip-tracing flow direct to Casey at cost. No markup, no agency margin on usage. These pass-through costs vary based on actual usage — WyoHouses deal volume, Bighorn capital raise volume, enrichment, and inference load determine the run rate. They must remain funded for the platform to operate and for Ainsworth Group to maintain daily access for build, maintenance, and support.
|
$5,500/mo
Begins at Workflow 1 production launch
|
|
Capital Raise Performance Share
Activates only when Workflow 2 (Capital Raising) goes live and only on attributable raised dollars — capital committed by investors who came through the Envoy + Scout outreach pipeline. No raise = no fee. For context: a FINRA-registered placement agent typically charges 5–7% plus upfront retainers, compliance overhead, and exclusivity requirements. This is 3%, no registration, no exclusivity, no minimums — and it only runs on what the platform actually sources.
|
3%
On attributable raise · Workflow 2 only
|
Bighorn's existing CRM has 749 contacts who attended SquadUp 2026. If Workflow 2 calls those contacts during the first 90 days of production and reactivates four with average commitments of $50K each, the math runs:
4 commits × $50K = $200K raised · performance share = $6,000
Same logic scales. If the platform sources $3M from the broader pipeline (NAPE Tier 1, SquadUp net-new, mailing list, referral mining) over 12 months, performance share is $90K against $3M of new AUM. Casey writes that check only after the capital is committed.
The system is cash-flow positive at WyoHouses deal two. At $50K net per Revive acquisition, two incremental WyoHouses closes cover Year 1 fixed cost entirely — before Bighorn's Workflow 2 raises a dollar. Workflow 1 carries the Year 1 economics. Workflow 2 is upside that only costs money when it produces. Everything after deal two is leverage you didn't have to hire.
The retainer is the management contract. The deployment fee is the build. To remove all ambiguity:
Ainsworth Group's daily time across Recon, Scout, Match, Envoy Mode 1, and Envoy Mode 2+3. Not capped by ticket count or call volume.
Prompt tuning, qualification logic adjustments, buy-box rule updates, model refreshes as performance data accumulates.
When an operator misfires, output drifts, or a list format breaks the pipeline — response time is hours, not days.
Weekly review cadence with Casey's team. WyoHouses deal queue health, Bighorn IR calendar quality, qualification rates against transcripts, attribution audit.
Bighorn's principal voice on what gets built next, what gets deprecated, and what gets prioritized. Co-development, not vendor management.
Cloudflare workspace operations, daily budget oversight against Casey's accounts, observability across every operator run, every call recorded and reviewable.
Three things are scoped separately, by design, so this proposal stays clean:
Optional follow-on engagement. Scoped once Phase 1 is producing and the CRM target is selected.
A separate operator (Vault) on the roadmap. Activation, scope, and economics addressed by separate proposal when it ships.
Distribution participation through Bighorn's network, partner program structure, and any co-branded edition terms — addressed by separate agreement at the principal level.
AI-native deal flow and IR infrastructure isn't a question of whether it becomes table stakes in private real estate. It already is — and the operators moving first are the ones building the data advantage, the investor relationships, and the compounding deal pipeline that compounds with every passing quarter.
The decision isn't whether to build this kind of operating system. The decision is whether Bighorn is one of the first funds running it — or one of the next fifty catching up to one that already does. The window where early commitment comes with locked rates, co-development input, and anchor terms closes when the next operator signs.
Every system has failure modes. The ones below are the failure modes for this one. Naming them is the first part of managing them — which is what the retainer funds.
Scout and Recon process what comes in. If WyoHouses' birddog network slows, the MLS feed degrades, or off-market lead volume drops below current run rate, the operators don't manufacture deals — they rank fewer of them. The platform multiplies whatever volume WyoHouses brings to it. If volume falls, Workflow 1 output falls with it. Mitigation: Scout's distress-signal sourcing is designed to add net-new inflow, not replace existing channels — but it's an additive layer, not a backstop.
Envoy Mode 1 can dial 4,000 contacts a month. It cannot make a non-investor accredited. The NAPE Tier 1 list, the SquadUp roster, and the Bighorn investor CRM are the inputs we have — and their conversion rates set the ceiling. Modeled qualification rates are projections, not guarantees. The first 60 days of production will produce real conversion data. Phase 2 conversations begin from real numbers, not modeled ones.
The 506(c) qualification logic screens for accreditation indicators, scores interest, and books calendar time. It does not replace the judgment call about which qualified investor is right for the fund at this stage of the raise. The closing conversation is still Bighorn's. The platform's job is to make sure that conversation happens with the right person, prepared, on the calendar. It is not an autonomous IR team.
A qualification prompt converting at 18% in Month 1 will reach 11% by Month 3 without recalibration against live transcripts. A skip-trace pipeline tuned for one list format silently misfires when the next format arrives. None of this surfaces as an error message — it surfaces as gradually softer output. The retainer exists because drift is the default state of an unmanaged AI operator. The work the retainer funds is catching drift before it compounds. Without that work, performance erodes quietly.
LLM inference, voice and telephony, enrichment, and skip-tracing are billed at cost — no markup. They scale with usage. Bighorn controls the ceiling by setting the daily budget. Ainsworth Group manages spend against that budget for output efficiency, but a 2× call volume month produces a 2× variable cost month. Modeled costs in this proposal assume current call volume targets; real run rate is set by Bighorn.
This proposal is bounded: two workflows, six weeks to first production, twelve-month retainer. It is not a five-year roadmap, an enterprise deployment, or a platform license. If Bighorn wants more — CRM integration, Vault lender matching, channel partnerships — those are scoped separately when each is ready. The deal is what the deal says. Nothing more is implied.
Workflow 1 should produce ranked deal flow within the first two weeks of production. Workflow 2 should produce qualified investor meetings on the calendar within the first week of outreach. Two incremental Revive closes cover Year 1 fixed cost. None of these are guarantees — they're the realistic targets the system is built to hit. The proof window is real. Read the numbers when they come in.
Both workflows are live, attribution data is accumulating, and the proof window produces real numbers against modeled estimates. Phase 2 conversations begin from that position — not from speculation. No auto-renewal. No roll-forward without mutual agreement. The retainer ends when Bighorn says it ends.