Enterprise field-service platforms are built for enterprises. Their small-business tiers are English-only, priced for shops with a controller, and none of them serve the operator who runs a bilingual crew off a phone. AgileService is our answer to that gap — currently in development, coding kickoff August 2026.
Workflows and UI in active design. Vertical selection locking in Q3 2026 with early design partners. Nothing on this page ships today — everything is a public commitment to what we're building.
Not because their owners are bad at running businesses. Because the software category hasn't served them.
The schedule is in WhatsApp, the customer address is in a text thread, the job photos are in the tech's personal camera roll, and the invoice gets written on the way home. Nothing is queryable, nothing gets audited, nothing survives an employee leaving.
No visibility into whether a tech is on-site, how long they've been there, what parts they used, or whether the customer signed off. The owner finds out at the end of the day — or the next morning, if the tech is still working.
Because the tech didn't capture the details, the office has to reconstruct them. Every reconstructed invoice risks a customer dispute — and every week of lag is cash that isn't in the account. Small operations run on cash, not receivables.
An operator whose crews speak Spanish or Portuguese in the field, and English with the office, needs both. The market leaders ship English-only or bolt on translation after the fact. AgileService is designed bilingual from the ground up.
Every card below is scoped for v1 and reflects the current design. Some workflows may change as pilot partners give feedback.
Every job is a work order with a customer, a location, a scope, materials, labor, and a paper-trail of every state change. The single source of truth for "what did we do, where, and when?"
Assign work to technicians by day and crew. Drag-and-drop schedule view for the owner or office. Route optimization for multi-stop days. Visible on the tech's phone the moment it's saved.
Everything a technician needs to complete a job from a phone: work-order details, customer history, photo capture, parts consumption, signature, mark-complete. Works offline; syncs on reconnect.
Every customer, every site, every asset. Full service history queryable from any job. "Have we been here before? What did we do? Who signed?" — answers in one screen.
Invoice generated from the completed work order, no re-entry. Standard payment methods for the market. Overdue tracking and reminder workflow. Cash arrives when the job ends, not weeks later.
Techs work in basements, remote sites, or rural areas. The mobile app captures everything offline and reconciles cleanly when signal returns. Same guarantee that keeps AgileWeight running through network outages.
The incumbents (Jobber, Housecall Pro, ServiceTitan) miss at least three of these. That's the whole reason we're building AgileService.
Every screen, every notification, every printed doc originates bilingual. The English office writes work orders; the Spanish crew reads them on their phones. Same data, both languages, no lag on translations.
Every customer gets a real 30–60 minute onboarding call with the founder or an engineer. Not a video tutorial. Not a chatbot. Someone sits with you and gets your first work order into the system.
WhatsApp threads, Google Sheets, half-finished job trackers — you send us what you have, we structure it into AgileService before you go live. No "upload your CSV" self-serve trap. Founder-led delivery.
The in-product assistant, auto-detection helpers, and retrieval-grounded help all ship in the first release. Nobody gets "AI features are coming next quarter." When v1 ships, the AI ships with it.
Techs work through no-signal conditions — basement jobs, rural routes, dead-zone sites. Everything queues locally, syncs deterministically when signal returns. Zero lost work. Inherited from AgileWeight's offline queue.
The one thing you won't find in ServiceTitan, Jobber, or Housecall Pro at any price.
The owner writes work orders in English; the tech reads them in Spanish. Field photos, notes, and signatures round-trip in whichever language the person on that end prefers. Same data, two languages.
Estimates, work orders, invoices, and receipts print in the customer's language. Set once per customer, applied automatically to every document.
Every screen is designed with both languages in mind — no cut-off labels, no awkward line breaks, no "Sign In" button that becomes "Iniciar Sesión" and breaks the layout. Same quality bar as English on every screen.
AgileService inherits the architecture and reliability posture we've been shipping in AgileWeight for years. This is the shortest path from "planned" to "in production."
The offline queue and idempotent resync that protect AgileWeight against network drops carry directly into AgileService. Field techs can work through no-signal conditions with the same "zero lost, zero duplicated" guarantee.
The four-front security hardening completed for AgileWeight in July 2026 — unique credentials per installation, server-side data integrity, minimal network surface, defense in depth — is the baseline AgileService starts from, not a future goal.
The BYOK LLM assistant we ship in the current AgileWeight release (bring your own key, cascading providers, offline fallback, strict data minimization) is a candidate to extend into AgileService — with the same trust architecture, not a re-invention.
The vertical we launch in gets decided by who shows up. If you run a small field-service operation — three to twenty technicians, bilingual crew, tired of running the business out of WhatsApp — we want to talk to you.
An hour a month for design review calls between now and the coding kickoff. Later, a willingness to run early builds in a small corner of your operation during 2027 and tell us honestly what's wrong.
The product shaped to your workflow, not somebody else's. Priority pilot access. Meaningfully discounted licensing for the first two years of production use. Direct line to the engineering team through v1.
Or email us directly. We're a small team; the message reaches the founder.
A page for a product that doesn't exist yet should be clear about what's real.
No. AgileService is in design. There's no login, no download, no sandbox. When there is, this page will say so.
Not announced. Pricing follows the vertical selection and the pilot feedback. We'll publish it before v1 ships.
Home renovation services — painting, remodeling, cleaning, and adjacent trades. An underserved sector traditionally worked by minority-owned contractors, where existing field-service tools were built for larger, English-first operators. Roadmap expands to building and construction as the product matures.
30-day free trial, credit card required, full platform access. A permanent free tier doesn't drive real adoption in field-service software — the industry poster child (JumpCloud) walked away from theirs in mid-2025 for exactly this reason. We'd rather charge fairly than run a bait-and-switch.
Every field-service tool offers a 30-day trial. The differentiator isn't the trial format — it's what happens in those 30 days.
Day 30 is running your business, not still learning the tool.