Internal Strategy/For the AuxBOS team/22 August 2026

AuxBOS:
how we make it pay.

Everything the US research turned up, in one place: what to keep, fix and cut, every way we could price it weighed honestly against each other, who we sell to, and exactly how the cold-call engine runs. Built so you three can decide, not so anyone decides for you.

The target
US marketing & creative agencies. Best product fit, no compliance wall, they already pay for all-in-one.
The engine
Commission cold-callers + a trained closer. Rehman’s CJ network + sales-manager experience is the fuel.
The decision
Which pricing model to lead with. Section 03 lays out all of them, pros and cons, so we pick together.
00Straight talk

Where this stands, no sugar

The honest read

AuxBOS is a genuinely capable all-in-one business system, and the market it’s entering is crowded, not empty. Both are true. We don’t win by being the only one who does CRM + HR + finance in one place — Odoo, Zoho, and two free open-source tools already do that. We win on three things nobody else nails: the modules being one real system instead of five stitched apps, an honest sales and support motion, and going deep on one kind of customer — agencies.

The product is real: enforced multi-tenant auth, a working general ledger, three portals, mobile-responsive. It has one serious security bug (fixable in days) and needs a couple of integrations before it’s sellable. Nothing here is a reason not to do this. It’s a reason to fix a short list first.

The money question — is a company really going to pay a lot for a back-end system they can technically live without? — is the right question, and the answer is: only if we sell relief from a specific pain, to a specific customer, and only after we have a few reference clients. The price follows the pain, not the feature list. That’s what this whole document is built around.

01The market

What the US research actually said

We verified real 2026 pricing across the whole field. The takeaway: the “all-in-one” space is packed from free to $250 a seat — so our edge can’t be “we do everything.” It has to be sharper than that.

Who we’re really up againstPriceWhat it means for us
ERPNext / DolibarrFREEOpen-source, do CRM + HR + accounting. Proof breadth alone is not a moat.
Odoo$25–61/user/mo15+ years, deep, huge partner network. Sits where we want to.
Zoho One$37–90/user/mo45+ apps, real payroll in all 50 states. The incumbent to beat on trust, not features.
GoHighLevel$97–497/moOur closest role model — won agencies with all-in-one + a reseller army. Study this one.
CodeCanyon scripts (ERPGo etc.)$59–99 one-timePHP all-in-ones with our exact pitch, sold cheap. The floor of the market.

All prices verified against vendor pages, August 2026. Full sourced research in the team folder.

On “basically Salesforce, but better”

Half-true, and worth being precise about so we don’t get caught overclaiming. Salesforce genuinely does not natively do HR, payroll, or accounting — a Salesforce shop stacks three separate vendors and pays $300–500 per user per month. So “one login for what Salesforce bills you three ways for” is a real, true line. But Salesforce isn’t our competition — Odoo and Zoho are, and they already do the all-in-one thing. We should use the Salesforce line as a hook, never as the core claim. Overclaiming is exactly what’s driving buyers off Odoo right now (four “is Odoo a scam” threads in under a year). Honesty is our edge; let’s not spend it.

The one gap worth everything. Across every incumbent, users say the same thing: “one system” is a lie — getting a quote to become an invoice to become a project requires a paid consultant, because the modules are parallel apps under one login, not one database. If AuxBOS is genuinely one data model where a record flows through the whole business with no glue code, that is the product. That’s the first thing we need to confirm internally (Q1 at the end).

And the second edge Rehman is right about: it’s fully customizable

This is the pitch we center on, and it’s honest. Odoo, Zoho, HubSpot — you configure inside their box, and any real change means hiring a $150/hour consultant and waiting. Because we are the ones who built AuxBOS and we do the customizing as part of the deal, we can promise something none of them can at this price: the system is molded to exactly how the client’s business runs — rename anything, add fields and workflows, turn modules on or off, or have us build what they’re missing — included, done for them, no third party.

Every other subscription is a rented template. Ours is their system. That’s a real differentiator, it’s true, and it’s the one thing a cold caller can say in one sentence that no competitor can match. It leads both the pitch and the buyer doc.

02Keep / fix / cut

What to do to the product before we sell it

Ranked. Number one is non-negotiable — everything else waits behind it.

  • 1
    Fix the stored XSS. This is the only true emergency.A value saved in one field executes as live code in an admin’s browser later — confirmed by test, then cleaned up. 15 of 23 front-end modules build HTML from raw data with no escaping. Escape on output or sanitize on write. Days of work. Until it’s done we cannot responsibly hold a client’s data, and any buyer’s tech reviewer will find it.
  • 2
    Build the checkout — both halves. This is a money-maker, not a chore.(a) Real payment so customers can pay us. (b) Let our clients collect payments on their own invoices via Stripe Connect, and we take a small cut of every dollar. See section 06 — the second half is the biggest passive-revenue lever in this whole plan.
  • 3
    Ship 2–3 integrations: QuickBooks, Google Workspace, a webhook/Zapier hook.“Customize it to the business” almost always means “connect it to what they already run.” This is the gap that kills agency deals on the second call — and it’s also something we can charge to build.
  • 4
    Move the login token out of the URL; add security headers.An afternoon each. Standard hardening any reviewer checks.
  • 5
    Rename “Payroll,” “Tax,” and the MACRS/compliance labels to what they honestly are.“Salary Records,” “Compensation,” “Expense Categories.” US payroll is a regulated activity we don’t do; agencies don’t buy us for it anyway. Don’t claim it.
  • 6
    Fix the page titles (“HRM Admin” / “Standalone CRM”) and scrub demo copy before any live URL.And settle who owns the underlying template license — Q2.
  • 7
    Decide what the screenshot-monitoring feature is for. Include it, don’t lead with it.It sells to low-trust contractor shops and scares agencies. For our agency ICP, keep it as an optional module, not a headline.
  • 8
    Build the one thing that’s our whole edge: no-consultant cross-module flow.Lead → client → project → invoice → ledger, as one record, zero setup. If it already works this way, prove it in the demo. If it doesn’t, this is the most important thing to build.

What to cut or hide before we demo — dead weight that only hurts

Rehman’s right that some of this is just noise. Cutting or hiding it makes the product tighter, the demo cleaner, and stops us overclaiming:

  • The employee screenshot / activity tracker — this one is niche-dependent, not a blanket cut. For a BPO or call center it’s a headline feature (see section 04B) — keep it front and center. For client-facing verticals where it reads as creepy, hide it. Show the right modules to the right niche.
  • The “Strategic Finance Core” (treasury, tax, close, MACRS depreciation) — empty scaffold that overclaims enterprise features agencies don’t need and we don’t deliver. Hide it until it’s real, or cut it.
  • Half-built campaign / drip / automation shells and lead scoring — either finish them or hide them, so a live demo never hits a dead button.
  • Anything pointing at regulated verticals (real payroll tax filing, HIPAA, legal trust accounting) — multi-year builds, not customizations, not our lane.

Rule of thumb: if it doesn’t help sell an agency and it’s not finished, it shouldn’t be visible in the demo. A tight system that does eight things perfectly beats a bloated one that does twenty things halfway.

03The pricing

Every way we could sell it — weighed against each other

This is the decision. Five real business models, each with its natural pricing structure, honest pros and cons, and a call. Read all five, then we pick. My lean is flagged, but the choice is ours together.

A · Productized: setup fee + monthly retainer

My lean
$3–15K setup · $500–2K/mo

Sales-led, mid-ticket. We charge a one-time fee to stand it up and configure it for the agency, then a monthly retainer for hosting, support and small changes. Tiered Good/Better/Best. This is the sweet spot: high enough per-deal to pay commissions, low enough to actually close, light enough to fulfill without a custom build every time.

Pros

  • Easiest five-figure deal to close
  • Recurring revenue from day one
  • ACV high enough to feed cold-callers
  • One core product, configured — not forked

Cons

  • Still a real sales effort per deal
  • Retainer must be mandatory or it decays into free support
  • Needs the demo + closer training dialed in

B · Full custom high-ticket build

Later / bigger clients
$15–75K build · $2–6K/mo

The Odoo/NetSuite-partner model: big upfront to build it around the client’s exact workflow, plus a fat retainer. Best ACV in the whole menu. But heavy fulfillment (real dev per client), harder close, and it genuinely needs reference customers first — nobody hands a no-name vendor $50K without proof.

Pros

  • Highest revenue per deal
  • Deep customization = sticky client
  • Justifies a white-glove sales motion

Cons

  • Every client risks becoming a forked codebase we can’t maintain (the “services trap”)
  • Long sales cycle, needs references
  • Fulfillment eats the cousins’ dev time

C · Self-serve SaaS (GoHighLevel-style)

Phase 2
$99–499/mo flat, or $20–80/seat

Anyone signs up on a website, adds their team, pays monthly. Scales infinitely with no per-deal sales effort. But this is a marketing-and-product business, not a sales business — it needs a content/ads/affiliate machine and a product that onboards itself, neither of which we have yet. It also needs the checkout built (section 06) before it can even function.

Pros

  • Scales without adding salespeople
  • Predictable recurring revenue
  • Huge ceiling if it catches

Cons

  • Needs a marketing engine we don’t have
  • High CAC, low-price plans churn hard (~68%)
  • Product must onboard itself — ours needs setup
  • Doesn’t use our real weapon: the sales team

D · White-label to agencies (reseller)

Strong side-bet
$297–497/mo per agency

Sell it to agencies who rebrand it and resell it to their clients under their own name. This is exactly how GoHighLevel prints money. It solves our biggest weakness — no brand — because the reseller’s brand carries the trust. Could run alongside model A.

Pros

  • Solves the no-brand problem structurally
  • One deal = many end-users
  • Recurring, and the reseller does the selling

Cons

  • Needs solid white-label / multi-tenant polish first
  • Support load can climb fast
  • You’re one step removed from the end customer

E · Hybrid / phased (how I’d actually run it)

The real answer
A now → C or D later

Lead with A (setup + retainer, sold by the cold-call team) to get paying agency references and learn exactly who buys and why. Layer in the payment rake (section 06) on every client from day one. Once we know what converts and the product onboards itself, open C (self-serve) and/or D (white-label) as expansion. Don’t run everything cold — earn the right to scale.

Pros

  • Uses our actual strength now (sales)
  • Builds proof before scaling
  • Keeps the big-ceiling models open for later

Cons

  • Requires discipline not to chase everything at once

The raw pricing mechanics (mix and match inside any model)

LeverReal rangeNote
Setup / onboarding fee$3–15KOne-time. Funds the hand-holding a new vendor must give.
Monthly retainer$500–6K/moHosting + support + small changes. Make it mandatory.
Tiered plansGood/Better/BestAlways. Three options anchors the middle one.
Per-seat$20–80/user/moOnly for a self-serve tier. Too low-ACV for cold-callers alone.
Payment rake0.5–1% of volumeThe sleeper. Passive, scales with client success. See 06.
Change-order dev$150–250/hr billedCustom work beyond the retainer, signed before we build.
White-label wholesale$297–497/moPer reseller agency, unlimited sub-accounts.

The honest number, because Rehman asked. The $50–150K figures are real for the category — but they go to established vendors with references. On day one we will not close $50K deals. Realistic first 5 clients: $3–10K setup + $300–800/mo, priced low on purpose to buy proof. After references: $10–25K + $1–2K/mo. Big clients later: $30–75K. And there’s a floor — commission-only selling stops paying below ~$5–8K a deal, because the closer’s cut gets too small. That floor is the reason we can’t go cheap and keep a sales team, and the reason mid-ticket (model A) is the answer.

04The customer

Who actually needs the whole thing

I was wrong to lead with marketing agencies, and Rehman’s agency buddies are why. A lean agency is client-heavy but not workforce-heavy — no HR team, no attendance, no payroll headache — so half of AuxBOS is dead weight to them. The product only earns a five-figure price when a business needs all of it. So the real question isn’t “who serves clients,” it’s “who runs a real hourly workforce and serves clients and delivers work and bills for it.”

The Need Matrix — score every candidate on five axes

AxisThe questionWhere agencies fail
WorkforceEnough employees that HR, attendance, scheduling & payroll genuinely matter?FAIL — tiny team
ClientsReal customer relationships needing a pipeline + portal?Pass
DeliveryJobs / projects / service work to assign and track?Pass
MoneyThey invoice and run their own books?Partial
OpeningNo dominant cheap all-in-one already owns them?FAIL — GHL owns them

The businesses that score high on all five are boring, labor-heavy service businesses. And here’s the tell that confirms it: AuxBOS is unusually heavy on HR, attendance, and employee screenshot-tracking. That’s not a quirk — it’s a fingerprint of who it was really built for. The product has been pointing at its true customer the whole time: operations that run a big hourly workforce.

The sweet spot: 25–75 employees, $3–15M revenue

Verified from the research: real pain starts around 15 employees (informal HR breaks), turns acute and budget-justifying at 50 employees / $8–15M (ACA & FMLA compliance cliffs, QuickBooks straining). Below 15, no pain; above ~100, the enterprise incumbents (Bullhorn, WinTeam, ServiceTitan) take over. The 25–75 employee band is our zone — big enough to feel it and afford $5–30K, too small for the enterprise tools to bother with.

Two hard rules the research forced on us

  • Integrate payroll, never build it. Staffing, construction (Davis-Bacon), and home care (Medicaid) all have regulated tax/compliance filing. We connect to a payroll processor — we do not become one. Keeps the “one system” pitch honest.
  • Never fight a vertical where an excluded function IS the product. Field-service and moving = dispatch/routing is the product (we don’t do it). Home care = EVV/Medicaid is mandated. Stay out of those; we’d be a worse core with a bolt-on.

The positioning line, near-verbatim from the staffing industry’s own 2026 research: “One system that moves your data in real time, instead of five systems that email each other.” Point that at a business drowning in a real workforce, and it’s a painkiller with a dollar figure attached.

04BThe list

The compiled target list, scored and ranked

Three research threads, cross-checked. Ranked by need fit × how soft the incumbents are × how easy they are to find. This is the list to hand a sales team.

Tier 1 — point the first dials here

VerticalUS sizeWhy it wins
BPO / call centers (50–500 seats)low thousandsThe single best fit found. Their workforce data IS their billing data (they bill clients per staffed hour/seat). The screenshot-tracking feature is a core requirement here, not a liability. Today they stitch a monitoring tool + Excel + CRM and undercharge clients from bad reconciliation — we stop provable revenue leakage.
Staffing / recruiting agencies (<75 staff)~27,000Cleanest 4-for-4: the agency is the employer of record for a huge managed workforce. Bullhorn is expensive & gappy (billing 3.0/5, mobile 1.6/5), none bundle a real ledger. Their own industry says it’s converging to “one system.” Proven reseller channel exists (staffing SI consultants). Integrate payroll.
Commercial janitorial / facilities (20–150 staff)~53,000Most fragmented vertical, clearest dead zone: cheap tools (Swept) skip payroll/GL entirely; the only full ERP (WinTeam) serves 100+ and scores 1.0–1.5/5 on payroll & mobile from its own customers. 50–100% turnover makes the HR case concrete.
Security guard companies (20–150 guards)~12,500Best functional fit (100–150% turnover, per-site billing) AND a timely displacement: Trackforce’s 2026 rebrand folded Silvertrac (the SMB favorite) into an enterprise-first platform, orphaning exactly our-size customers right now. A warm list this quarter.

Tier 2 — strong, test right after

VerticalUS sizeWhy it’s here
Manufacturing job shops / fabricators~20–24K shopsCleanest job = project = invoice mapping. Shop-ERPs ignore HR/CRM. NIST MEP (1,400 advisors, all 50 states) is a ready-made referral channel.
Restoration & remediation~60,000Crews + insurance/TPA clients + multi-week jobs + billing. Quantified pain: 8–15 hrs/week lost to manual work. Dual insurance-carrier CRM nobody models.
Construction subs (private-commercial, W-2 crews)subset of ~490KReal gap between Procore (too big) and Buildertrend (wrong fit). Target 15–100 W-2 crew, avoid government / certified-payroll work.
Independent insurance agencies (10–50 staff)fragmentedSleeper. Producers (workforce) + policyholder book (CRM) + renewals/claims (delivery) + commissions (billing). AMS360/EZLynx do policy data only; the rest is QuickBooks + spreadsheets.

Tier 3 — overlooked, worth a probe once Tier 1 is proven

Veterinary groups (multi-DVM, cash-pay heavy), trade/vocational schools (sub-500 students, stuck between heavy SIS and spreadsheets), non-profits with paid staff (very overlooked, but budget-constrained & slower), med-spa chains (PE roll-up wave, but position behind the booking tool, not against it), catering/events companies (documented CRM-vs-staffing seam).

Do NOT waste dials here. Field services & movers (dispatch is the product, out of scope), home care (EVV/Medicaid lock-in), property management (the “workforce” is 1099 vendors, and the software is cheap & commoditized), and fitness / auto repair / landscaping / fitness studios / childcare (mature, well-funded incumbents already own the workflow). Churches don’t invoice at all. These fail the Need Matrix or the Opening test.

05The leads

Where to source each list, and the channel play

The good news about targeting boring workforce-heavy verticals: they live in trade associations and licensing boards with real directories and real phone numbers — far cleaner lists than scraping agencies, and TCPA-friendly business landlines.

The general engine (works for any vertical)

  • Apollo.io / ZoomInfo — filter by the vertical’s NAICS code + headcount 25–100 + owner/ops-director titles. Verified phones, exportable.
  • State licensing boards — for security, home inspection, trade schools, contractors: public, complete, free lists of exactly the licensed operators.
  • LinkedIn Sales Navigator — to pull the owner/COO name before the dial.

The specific directory for each Tier-1/2 vertical

VerticalWhere to find them
BPO / call centersIAOP, ContactCenterWorld (230,000 members), Customer Contact Week attendee lists, LinkedIn Sales Nav NAICS 561422 at 50–500 staff
Staffing / recruitingAmerican Staffing Association (ASA) directory, Bullhorn Marketplace partner list, state staffing associations
Janitorial / facilitiesBSCAI (1,000+ member firms), ISSA, CleanLink trade press
Security guardState security-licensing boards (best list), ASIS International, warm Silvertrac-refugee lists
Manufacturing job shopsNTMA (1,000 members, 26 chapters), PMA, FMA / FABTECH, Thomasnet, and NIST MEP as a referral partner
RestorationRIA member directory, IICRC Certified Firm Locator (~6,000 firms), TPA vendor networks (Contractor Connection, Alacrity)
Construction subsABC & AGC chapters, trade-specific associations, state contractor boards
Insurance agenciesBig “I” (IIABA), state agent associations

The channel play — two proven reseller models to layer on

These already exist for exactly this kind of software, so we’re plugging into a motion, not inventing one:

  • Staffing / implementation consultants (like the firms doing Bullhorn implementations) — the closest-matching precedent. They already sell $5–30K project engagements to our exact buyers.
  • Bookkeeping firms & QuickBooks ProAdvisors — a decades-proven partner-reseller model; they resell + implement business software to SMBs and hold the trust.
  • MSPs as a channel, not just a customer — they already support the IT of janitorial, security and contractor firms, so they have the relationship. Unproven for a business-ops platform, so treat it as a bet to build, not plug into.

The five-point qualifier & the data play (unchanged and still the point)

Before pouring dials into any vertical, it must pass: can they pay (25+ staff / $3M+), do they feel the pain (a real workforce + disconnected tools), big enough list, reachable by phone, and already buys software. Fail two, drop it.

The data play — how we actually find THE niche. Don’t crown a winner in a meeting. Pull a seed list of 2,000–5,000 across two or three Tier-1 verticals, run the callers, and track which vertical, city and script converts. After 2–3 weeks the dials tell us where the money is — pour budget into the winner, cut the rest. My bet is BPOs or staffing lead, but the phones decide, not us. Build the tracking sheet day one: vertical, source, dials, connects, appointments, closes.

06The engine

Running the cold-call machine

Rehman’s instinct is right and the math holds up. Here’s the honest version, the team shape, the money, and the two things that actually decide whether it works.

The funnel, run against real benchmarks

Rehman’s plan: ~10 callers × 100 dials = 1,000 dials/day. Real numbers say that’s a little conservative, which is good:

1,000Dials/day
10 reps × 100
~280Connects
~28% answer
10–25Appointments
booked/day
1–3Closes/day
at full ramp

Benchmarks: ~28–32% connect rate, ~2.3% dial-to-meeting (6.7% for top reps), 10–20% of demos close. Rehman’s “1 close per 1,000” is a fair, slightly conservative planning number. Early, with green reps and a cold offer, expect closer to 1–3 per week until the script and demo are dialed.

The team, and who gets paid what

RoleJobPay (1099, commission)
Cold callers × 5–10Dial, gauge interest, book the appointment$25–75/booked appt, or ~2–5% of the deal
Closer × 1–2Run the demo, handle objections, close10–15% of the deal
Fulfillment (cousins)Onboard, configure, supportCovered by setup fee + retainer

On a $12K deal, that’s ~$1,500 to the closer and $300–600 to the caller who set it — real money that keeps commission-only reps dialing, which is the whole reason this only works at mid-to-high ticket. At $99/mo it would never pay a human to call.

A rough monthly picture

Illustrative month (conservative ramp)Amount
Deals closed (say 8 at $10K setup + $800/mo)$80K setup + $6.4K new MRR
Sales commissions (~20% of upfront)−$16K
Dialers + data + numbers (10 seats)−$2–3.5K
Fulfillment (offshore dev, low)−$4–8K
Rough gross left, month one~$50K + growing MRR

Illustrative, not a forecast — real numbers depend entirely on close rate and ramp. The point: even a conservative month clears the costs comfortably, and the MRR + payment rake compound underneath.

The legal three lines (get these right)

  • 1099 contractors, set their own hours, own tools. Keep them independent, not scheduled employees. Rehman is in PA, not California — so AB5, the law that would blow this up, doesn’t apply. Still worth a quick lawyer sign-off before scaling past a handful.
  • The compliance trap is TCPA, not Do-Not-Call. B2B calls to a business landline are DNC-exempt — fine. But there’s no B2B exemption for autodialed calls to cell phones, and lead lists are full of mobiles. Manual dialing and prioritizing business landlines is the safe lane.
  • Own the script and the recording policy. Standard, cheap, keeps everyone clean.

The two things that actually decide it

1. The list and the script beat dial volume. Cold-calling “want a business system?” to random companies converts like garbage. Cold-calling a targeted list of agencies with “you’re paying for five tools that don’t talk — we replace them with one” converts many times better. Build the agency list, write the pain-first script.

2. The closer is the bottleneck, and Rehman already knows it. High-ticket + a software demo means the closer needs real training and a tight, repeatable demo. This is where Rehman’s CJ network and sales-manager experience is the actual edge — and where the buyer-facing overview doc (the second PDF) becomes the closer’s weapon.

07The money lever

The checkout — and why it’s bigger than the software fee

Rehman flagged this and he’s right to. There are two versions, and the second one quietly turns a software company into a payments company — which is worth several times more.

Version A — AuxBOS charges its customers

Real Stripe checkout built into the product so agencies can sign up and pay us directly. The mock billing system already scaffolded in the code anticipates this. Required for any self-serve tier, and it makes our own billing clean either way.

Version B — our clients collect payments inside AuxBOS

Wire Stripe Connect into the invoice module so an agency’s clients can pay their invoices right in the system. Two things happen: the invoicing feature becomes genuinely useful (now it competes with QuickBooks and Stripe Invoicing instead of just generating PDFs), and — the important part — we take a rake, 0.5–1%, on every dollar that flows through.

Why this is the sleeper. An agency processing $100K/month in client invoices through AuxBOS = $500–1,000/month to us, passively, on top of the retainer, and it grows as they grow. This is exactly how Jobber, Housecall Pro and Square make their real money — payments, not software fees. A software business trades at a few times revenue; a payments business trades at far more. Building version B is the single highest-leverage thing on the roadmap after the security fix.

Do both. Version A to get paid; version B because it’s the revenue stream that scales without a single extra sales call.

08Decide

What we decide together, and what the cousins confirm

Two buckets. The first is the strategic calls the three of us make as partners — nothing here moves until we agree on these. The second is the technical answers only the cousins have.

Calls we make together (the meeting agenda)

  1. Which pricing model do we lead with?Section 03. My lean is A now (setup + retainer), C/D later — the hybrid. But this is a partner decision, so it’s on the table, not decided.
  2. What’s our opening price for the first five clients?I’d go low on purpose — $3–10K setup + $300–800/mo — to buy references, then climb. Do we agree, or anchor higher?
  3. Which niche do we point the callers at first?Section 05. Web dev / SEO / branding agencies to start, and use the data to find the real winner. Agree on the seed niche and the tracking sheet.
  4. Who runs the closing, and how do we train them?Rehman’s CJ network + sales-manager role is the edge here. Who’s the first closer, and what’s the demo script + comp?
  5. What do we cut or hide from the product before we demo?Section 02. Sign off on hiding the tracker, the empty finance scaffold, and the half-built shells.
  6. How do we split the money and the roles?Sales/GTM vs build/fulfillment vs support. Worth agreeing on early so nobody’s surprised.

Technical answers only the cousins have

  1. Is it truly one shared data model, or separate modules stitched together?This is our entire edge (section 01). Does a lead genuinely flow into a client, project, invoice and ledger as one record, or is that glue code? Confirm it — the pitch depends on it.
  2. Who owns the code, and was any of it bought?The “HRM Admin” / “Standalone CRM” page titles look like an extended template, and there’s a $69 CodeCanyon tier doing nearly this. If a license sits underneath, it governs whether we can resell or white-label at all.
  3. How fast can a customization ship, and does it fork the code?The whole model’s margin lives here. One core configured per client = scalable. Ten forks = we drown. What’s the honest turnaround on a workflow change?
  4. Can we take a US client payment today?Pakistan is restricted on Stripe/Mercury. The fix is a US LLC + a merchant of record (Paddle), or routing through the US entity. This gates our first invoice — let’s know where we stand.
  5. Is the screenshot-capture desktop agent real, and is V2 shipping or a mockup?Both change what we can honestly show a buyer.
Basis. Hands-on testing of the live application (created and deleted test records, probed auth, tenancy, validation, and output-escaping — nothing left behind), plus four research threads on the sell-and-customize market, the competitive landscape, high-ticket lead generation, and offshore-vendor economics. All pricing verified against vendor pages, August 2026. Full sourced research is in the team folder.

AuxBOS US Playbook · internal · 22 August 2026 · for the AuxBOS team · a plan to argue with, then execute.