Axle reads your technicians' field texts, writes the data into Jobber or Housecall Pro, and delivers your morning briefing before the first truck rolls. No new apps. No training. No behavior change.
Every evening, you or your office manager spend two hours decoding what your techs actually did. Invoices go out Thursday for work completed Monday. AR slips.
You've looked at hiring an ops manager. A good one costs $65,000 a year and won't stay long. So you keep doing it yourself. Again.
Ray texts the shop number the way he always has — in his own words, between jobs, from his truck. No app, no form, no tagging.
The message is interpreted, validated, and posted to Jobber or Housecall Pro. Ambiguous items get a quiet confirmation back to Ray. Every decision is logged so you can see exactly what Axle did and why.
At 5:47 AM, before the first truck rolls, you get the read-out: completed jobs, what's running late, AR status, and anything that needs a decision before 8 AM.
Runs at 5:30 AM. Owner gets yesterday's revenue, jobs completed, unresolved issues, and today's full schedule. Each tech gets their individual job list. The first thing you see every morning — the thing that makes Axle feel like an employee, not software.
Tech texts naturally — “finished the AC at Johnson's, needed a new capacitor” — and Axle parses it into structured data and writes it to Jobber or Housecall Pro. Your tech never opens the FSM app. This is the behavior-change-free data capture that solves the root problem: garbage job data.
Catches uninvoiced jobs 24 hours after completion, invoices overdue 30+ days, Jobber jobs closed with no QuickBooks payment after 48 hours, and techs who haven't updated an overdue job. Texts you the moment something needs attention.
Text a natural-language question about your business — “how much did we do last week,” “what's Marcus's numbers this month” — and get an answer from your actual data. This is the moment you realize you've stopped needing to open a dashboard.
Once you have 30 days of data, it starts building operational baselines — tech performance trends, job duration patterns, callback rates. Weekly insights on what's changing before it becomes a problem. The beginning of compounding intelligence.
Your tech is standing in a customer's driveway. Customer asks “how much for a new water heater?” Your tech texts Axle: “quote for 50gal water heater install at 123 Main.” Axle replies in seconds with a price range calibrated to your last six months of completed jobs — not an industry average, not a guess, your actual pricing patterns. Activates at day 45, once enough jobs and invoices have synced. Until then, it's in learning mode — watching your data, not quoting from it.
It doesn't feel like software. It feels like you hired six people in twenty minutes.
Auto-detects unsent invoices, unfollowed estimates, and missed upsells. Triggers follow-ups automatically. If it finds $3,000/month in leaked revenue, the $2,000 price pays for itself before month's end — with immediately calculable ROI.
Jobber job closed with no QuickBooks payment after 48 hours? You get an SMS with the unreconciled total. No waiting until the end of the month to discover three jobs never got billed.
Every estimate informed by the real cost and duration of every job you've completed. Rough averages on day one, accurate by month three, a pricing advantage by month six — one a static pricebook or a competitor's tool can't replicate.
Owner gets yesterday's revenue, jobs completed, and today's schedule. Each tech gets their personal day. Delivered before the first truck rolls.
Jobs completed, revenue generated, average ticket, revenue per hour — per-tech numbers delivered weekly by SMS. Week-over-week trending catches gradual declines before the revenue dip shows up in your bank account.
Reads your FSM calendar. Identifies underutilized trucks and techs sitting idle while jobs wait. Translates to a lost-revenue estimate. Reframes growth from "I need more techs" to "I'm not filling the capacity I already have."
Text a question — "how much did we do last week," "what's Marcus's numbers this month," "how many callbacks on AC installs" — and get an answer from your actual data. No dashboard, no SQL, no app.
Job status, line items, notes, and completion states written into your existing FSM. Axle reads the system of record. Doesn't replace it.
Every parse, every field written, every confirmation — logged in an irrevocable append-only ledger. When something needs review, you have exact receipts.
First ten days, Axle parses everything but writes nothing. You see exactly what it would have done before it touches your real data.
At 3 – 4% operational leakage on a $2M shop, the first recovered invoice covers your first month. The rest is upside.
Documented express written consent from every technician, every owner, captured during onboarding. Internal messaging only — customer-facing SMS is intentionally out of scope.
Numbers registered as verified business messaging under a verified brand. No 30% carrier filtering. Briefings arrive when they're meant to.
Ownership, export, and deletion rights belong to the shop. Aggregated insights Axle retains are explicitly separated from customer-specific data in the terms of service.
Customer PII in message bodies is encrypted at rest. Application logs are sanitized before writing. No plaintext customer addresses in error reports.
Message content is processed by Anthropic's Claude API. The full subprocessor list — Anthropic, Twilio, Supabase, Railway — is published and versioned, not buried in a policy PDF.
$1M cyber liability policy in force before the first pilot customer is onboarded. In the event of a data incident, protection extends beyond an LLC veil.
I'm Alex Valdez, 23, based in South Florida. My day job is helping franchise operators open new locations — training their teams, documenting how their businesses actually run. I've spent more time in small-business back offices than most people my age.
The pattern is always the same: operators pay $65,000 a year for office managers whose work is 80% decoding messages from the field, chasing invoices, and re-entering data across three separate systems. Every operator says the same thing — “I can't afford another person, but I can't grow without one.”
I pitched an AI solution internally. It was redirected to an internal tool. So I built Axle externally instead — with one conviction: a five-truck shop should be able to operate like a twenty-five-truck shop without the $200,000 in back-office headcount it usually takes to get there.
Thirty-day pilot. No credit card. Let's find out.
TCPA consent from your team. Jobber or HCP integration. Onboarding call. 10DLC brand registration under your business.
Axle parses every message and shows you what it would have written — but doesn't. You review daily until you trust the parse rate.
Axle writes to your FSM. Supervisor layer flags low-confidence parses for your review. Morning briefings start landing.
If Axle saved you real time, we move to an annual contract, quarterly billed. If not, you walk. No credit card required upfront.
No credit card for the pilot. No auto-renewal trap. Your data is yours to export at any point during or after the pilot. The only commitment is the one made after 30 days of working product.