BUSINESS REQUIREMENTS DOCUMENT
Roundtrip · A Traxs Company Product · Version 1.1 · August 2026
Business justification, stakeholder requirements, market analysis, financial model, and success criteria for the Roundtrip SaaS platform.
| Attribute | Value |
|---|---|
| Document Title | Roundtrip Business Requirements Document (BRD) |
| Version | 1.1 — Initial Release |
| Status | Draft — In Review |
| Product | Roundtrip — Field Service Management SaaS |
| Company | Traxs Company |
| Product Family | Waypoint · Relay · Roundtrip |
| Author | Business & Strategy Team |
| Date | August 2026 |
| Related Docs | PRD v1.0, SAD v1.0, Tech Stack Analysis v1.0 |
01 — EXECUTIVE SUMMARY
Executive Summary
Roundtrip is a multi-tenant Software-as-a-Service (SaaS) field service management platform developed by Traxs Company. It is designed to serve small-to-medium service businesses in trades and technical industries — HVAC, plumbing, electrical, auto service, appliance repair, and computer service — that currently manage their operations through a fragmented combination of spreadsheets, paper tickets, WhatsApp groups, and generic project management tools.
The field service management software market is a $5.1 billion global market growing at approximately 13% CAGR, driven by the digitisation of trade businesses and increasing customer expectations for transparency and professionalism. Yet the majority of small service businesses (fewer than 20 technicians) either cannot afford or do not fully adopt existing solutions due to pricing, complexity, or poor mobile experience for field technicians.
Roundtrip addresses this gap directly — combining the operational depth that dispatchers and business owners need with a mobile-first technician experience that requires minimal training. Its AI-powered route optimization and local LLM inference (via Ollama) provide differentiation that larger competitors do not offer at the SMB price point, while the multi-tenant architecture allows Traxs Company to operate the platform at low per-tenant cost.
Business Opportunity in One Paragraph
The North American field service SMB market represents approximately 400,000 businesses with 2–50 technicians that are underserved by current software. At an average subscription of $149/month per tenant, capturing 1% of this market produces $71.5M ARR. Roundtrip's AI-differentiated features, clean UX, and competitive pricing position it to realistically target 2,000–5,000 tenants within 36 months of launch.
| $5.1B | 13% | 400K+ | $149 |
|---|---|---|---|
| Global FSM Market Size (2025) | CAGR through 2030 | < Underserved SMB Businesses (NA) | Target Monthly Price (Standard Tier) |
02 — BUSINESS CONTEXT
Business Context
The Problem
Field service businesses — HVAC contractors, plumbers, electricians, computer repair shops, auto service businesses — share a common operational challenge: coordinating the movement of skilled technicians between multiple client locations each day while accurately tracking parts consumed, billing for work completed, and maintaining service records that enable better repeat-visit service.
The majority of small and mid-size businesses in this space manage this coordination through a patchwork of tools that create friction, errors, and lost revenue:
| Current Approach | Pain Point | Business Impact |
|---|---|---|
| Paper job sheets / carbon copies | Lost tickets, illegible handwriting, no search capability | Unbilled jobs, disputes with clients, hours of admin work |
| Spreadsheets for scheduling | No real-time updates, version conflicts, no mobile access | Double-bookings, technicians calling office for updates |
| WhatsApp / SMS for dispatch | No record-keeping, can't search history, no structure | Lost instructions, no audit trail for disputes |
| Generic invoicing tools (Wave, FreshBooks) | No integration with job data, manual re-entry | Billing delays, errors in line items, time-consuming |
| Paper inventory logs | No real-time visibility, frequent stock-outs on jobs | Return visits, customer dissatisfaction, lost margin |
| Phone calls for client updates | Technician interruptions, office staff overhead | Lower productivity, poor customer experience |
The Opportunity
Several converging trends make this an ideal time to build and launch Roundtrip:
- Smartphone penetration among tradespeople is now near-universal, making mobile-first tools viable where they weren't five years ago
- Post-pandemic labour shortages have increased pressure on service businesses to maximise each technician's daily productivity — route efficiency has direct P&L impact
- Customer expectations for transparency (arrival notifications, online invoices) have risen sharply, and businesses that don't provide them are losing clients to those that do
- Local AI inference (Ollama, small language models) has matured to the point where SMB-grade route optimization and Q&A assistants are viable without cloud API costs
- The SaaS delivery model has reduced the barrier to entry — a well-built product can reach global customers with a small operations team
03 — COMPANY & PRODUCT CONTEXT
Traxs Company & Product Portfolio
Company Overview
Traxs Company is a software development business building productivity and management SaaS tools for specific industry verticals. Its strategy is to develop a portfolio of focused, high-quality SaaS products rather than a single broad-market platform — enabling each product to excel in its niche while sharing common infrastructure, brand equity, and go-to-market resources.
| Product | Status | Description | Target Market |
|---|---|---|---|
| Waypoint | In Development | Business Management | Any business type |
| Relay | In Development | CRM and client relationship management | Service businesses, consultancies |
| Roundtrip | In Development | Field service management — dispatch, routing, billing, inventory | Trades & technical field service businesses |
Traxs Ecosystem Advantage
Roundtrip is designed to integrate with Nexus (CRM) in a future release — allowing field service businesses to manage their sales pipeline, customer relationships, and field operations in a connected Traxs ecosystem. This creates upsell opportunity and reduces churn as switching cost increases.
Shared infrastructure (authentication platform, billing infrastructure, DevOps pipelines) reduces per-product operating cost and time-to-market for new features.
Roundtrip Positioning
Roundtrip occupies the mid-market position between two extremes:
| Competitor Type | Examples | Weakness Roundtrip Exploits |
|---|---|---|
| Enterprise FSM platforms | Salesforce Field Service, ServiceNow FSM, SAP FSM | Priced at $75–$300+/user/month. Complex implementations. Require dedicated admins. Overkill for SMBs. |
| Simple job management apps | Jobber, ServiceM8, Housecall Pro | Lack AI-powered routing. No local LLM assistant. Limited inventory depth. Generic branding. |
| Generic SMB tools | Google Sheets, Trello, Monday.com | Not purpose-built for field service. No map, no routing, no part tracking, no field-specific workflow. |
| Roundtrip (target position) | — | Purpose-built for field service SMBs at SMB pricing. AI route optimization included at no extra cost. Local LLM means no data sovereignty concerns. |
04 — STAKEHOLDERS
Stakeholder Analysis
Internal Stakeholders (Traxs Company)
| Stakeholder | Role | Key Interest | Influence |
|---|---|---|---|
| Traxs Founder / Owner | Product vision and strategy | Revenue growth, product quality, Traxs brand reputation | High |
| Development Team | Build and maintain Roundtrip | Clear requirements, stable architecture, reasonable scope | High |
| Sales & Marketing | Acquire tenants (future) | Clear value proposition, competitive pricing, demo-able product | Medium |
| Customer Support | Onboard and retain tenants (future) | Intuitive UI, good documentation, low support ticket volume | Medium |
External Stakeholders (Tenants & Their Users)
| Stakeholder | Role | Primary Need | Success Looks Like |
|---|---|---|---|
| Business Owner / TenantAdmin | Pays the subscription, sets policy | Visibility into the business, control over settings, financial reporting | More completed jobs per day, faster billing, fewer missed revenue opportunities |
| Dispatcher | Primary power user (daily) | Fast ticket creation and assignment, live visibility of field team | Less time on the phone, fewer scheduling conflicts, less manual coordination overhead |
| Technician | Field user (daily, mobile) | Simple job info, easy status updates, clear navigation | More time on jobs, less time on paperwork, fewer calls to the office |
| Billing Staff | Financial workflows | Accurate invoice data from jobs, fast delivery to clients | Invoices out same day as job completion, fewer billing disputes |
| End Client | Receives service | Professional communication, accurate billing, service history access | On-my-way notifications, clean invoices, confidence the business is professional |
Stakeholder Requirements Summary
| Stakeholder | Must Have | Should Have | Won't Accept |
|---|---|---|---|
| Business Owner | Complete job and billing data, financial dashboard, user management | AI insights, trend reports, Nexus CRM integration | Data breach, cross-tenant exposure, billing errors |
| Dispatcher | Live map, fast ticket creation and assignment, real-time status updates | Drag-and-drop dispatch board, saved filter views | Slow page loads, no mobile access, confusing UI |
| Technician | Simple mobile ticket view, offline capability, camera part capture | Voice notes, AI field assistant | Complex UI, mandatory internet connection, slow syncing |
| Billing Staff | Invoice from ticket, PDF export, email delivery | Payment tracking, aging report, bulk send | Invoice data not matching job records, manual re-entry |
| End Client | Professional notifications, clear invoices | Online invoice payment, service history portal | Spam notifications, confusing documents, data errors |
05 — MARKET ANALYSIS
Market Analysis
Total Addressable Market (TAM)
The global Field Service Management (FSM) software market was valued at approximately $5.1 billion in 2025 and is projected to reach $9.6 billion by 2030, representing a CAGR of approximately 13.5%. North America accounts for approximately 38% of this market ($1.9B), driven by the high density of independent trade contractors and service businesses.
| $5.1B | $1.9B | 13.5% | 400K+ |
|---|---|---|---|
| Global TAM (2025) | North America TAM (2025) | CAGR to 2030 | SMB Target Businesses (NA) |
Serviceable Addressable Market (SAM)
Roundtrip's initial focus is on North American field service businesses with 2–50 technicians in the following verticals: HVAC, plumbing, electrical, appliance repair, auto service, and computer/IT service. These businesses represent the segment most underserved by current software — too complex for free tools, too small for enterprise solutions.
| Vertical | Est. NA Businesses (2–50 techs) | Current Software Adoption | Opportunity |
|---|---|---|---|
| HVAC | ~65,000 | ~35% use purpose-built FSM | ~42,000 addressable |
| Plumbing | ~55,000 | ~25% use purpose-built FSM | ~41,000 addressable |
| Electrical | ~50,000 | ~30% use purpose-built FSM | ~35,000 addressable |
| Appliance Repair | ~40,000 | ~15% use purpose-built FSM | ~34,000 addressable |
| Auto Service | ~60,000 | ~40% use purpose-built FSM | ~36,000 addressable |
| IT / Computer Service | ~35,000 | ~20% use purpose-built FSM | ~28,000 addressable |
| Total | ~305,000 | ~28% average adoption | ~216,000 SAM |
Serviceable Obtainable Market (SOM)
Roundtrip's 36-month target is 2,000–5,000 active tenants, representing 0.9%–2.3% of the SAM. This is conservative relative to the opportunity but appropriate for a new entrant bootstrapping growth. At the midpoint (3,500 tenants) and blended ARPU of $175/month, this represents $7.35M ARR — a realistic target for a well-executed product with strong word-of-mouth in trade communities.
Competitive Landscape
| Competitor | Pricing (approx.) | Strengths | Weaknesses vs. Roundtrip |
|---|---|---|---|
| Jobber | $49–$249/mo | Strong brand in trades, good UX, established | No AI routing, no local LLM, pricing opaque, no data sovereignty |
| Housecall Pro | $59–$259/mo | Good mobile app, popular in HVAC/plumbing | Limited inventory depth, no AI features, data stored in cloud |
| ServiceM8 | $29–$349/mo | Good iPhone app, solid forms/checklists | iOS-only focus, no AI, limited reporting, AU-centric |
| Kickserv | $59–$299/mo | QuickBooks integration, good invoicing | Dated UI, poor mobile experience, no AI routing |
| Salesforce FSM | $75–$300+/user/mo | Enterprise-grade, AI-powered (Agentforce) | Unaffordable for SMBs, complex implementation, overkill |
| Roundtrip | $99–$299/mo (target) | AI routing included, local LLM (data sovereignty), modern UX, offline PWA | New entrant, no brand recognition, limited integrations initially |
06 — BUSINESS REQUIREMENTS
Business Requirements
Business Requirements define what the business needs Roundtrip to achieve — distinct from the product features (which are captured in the PRD). These are the non-negotiable business outcomes that the product must deliver.
BR-01: Multi-Tenant Commercial Operation
| Requirement | Detail |
|---|---|
| ID | BR-01 |
| Statement | Roundtrip must operate as a commercially viable multi-tenant SaaS service, capable of onboarding, billing, and supporting multiple independent business tenants from a single platform deployment. |
| Rationale | The entire commercial model depends on multi-tenancy. Without it, Roundtrip would require separate deployments per customer — making it economically unviable for a startup to operate and scale. |
| Success Criteria | System supports 500+ concurrent tenants. New tenants can self-onboard within 10 minutes. Tenant data is provably isolated (verified by automated security tests). Monthly recurring billing is automated. |
| Priority | Critical |
BR-02: Self-Service Tenant Onboarding
| Requirement | Detail |
|---|---|
| ID | BR-02 |
| Statement | New business owners must be able to register, configure, and begin using Roundtrip without any manual intervention from Traxs staff. |
| Rationale | Manual onboarding creates a bottleneck that limits growth and increases cost-per-acquisition. At scale, handling hundreds of onboardings per month manually is not viable. |
| Success Criteria | A new tenant can complete registration and create their first ticket within 10 minutes of discovering the product. Traxs staff involvement is zero for Standard tier onboarding. |
| Priority | Critical |
BR-03: Subscription Revenue Model
| Requirement | Detail |
|---|---|
| ID | BR-03 |
| Statement | Roundtrip must support a tiered monthly subscription model with automated billing, trial periods, and plan upgrades. |
| Rationale | Predictable recurring revenue is the financial foundation of a SaaS business. Ad-hoc or per-project billing does not provide the revenue visibility needed for business planning. |
| Success Criteria | Subscriptions are billed automatically via Stripe (or equivalent). Failed payments trigger retry logic and account suspension workflow. Plan upgrades take effect immediately. Revenue is reportable in real time. |
| Priority | Critical |
BR-04: Data Privacy & Sovereignty
| Requirement | Detail |
|---|---|
| ID | BR-04 |
| Statement | Tenant business data — client records, service history, pricing, inventory — must never leave Traxs-controlled infrastructure. AI features must use local inference. |
| Rationale | Many field service businesses serve regulated industries (healthcare facilities, government buildings) or simply have strong data privacy expectations. Using cloud AI APIs (OpenAI, Anthropic) would send client addresses and service details to third-party infrastructure — an unacceptable risk for these customers and a liability for Traxs. Local Ollama inference eliminates this risk and is a genuine competitive differentiator. |
| Success Criteria | All AI inference runs via Ollama on Traxs infrastructure. No tenant data is transmitted to external AI APIs. Data residency can be confirmed in writing to Enterprise tenants. Privacy policy accurately reflects data handling. |
| Priority | Critical |
BR-05: Operational Cost Efficiency
| Requirement | Detail |
|---|---|
| ID | BR-05 |
| Statement | The platform must be operable at a cost that enables sustainable gross margins as the tenant base grows from 100 to 5,000 tenants without linear cost scaling. |
| Rationale | SaaS unit economics require that infrastructure costs grow sub-linearly with tenant count. If costs scale 1:1 with tenants, there is no path to profitability at reasonable prices. |
| Success Criteria | Infrastructure cost per tenant is under $3/month at 1,000 tenants. The shared architecture (shared schema for Standard tier, single API deployment) achieves this without dedicated infrastructure per tenant. Hangfire background jobs reduce synchronous API load. |
| Priority | High |
BR-06: Regulatory & Legal Compliance
| Requirement | Detail |
|---|---|
| ID | BR-06 |
| Statement | Roundtrip must comply with relevant data protection regulations for the jurisdictions in which it operates, initially covering the United States, and optionally Canada and Australia as those markets are entered. Traxs is incorporated as a US entity (Wyoming LLC or Delaware C-Corp). |
| Rationale | Non-compliance exposes Traxs to regulatory penalties, erodes customer trust, and can block sales to regulated industries. |
| Success Criteria | Privacy policy and terms of service are reviewed by legal counsel before launch. Data retention and deletion capabilities support CCPA and applicable US state privacy law rights-of-erasure requests; PIPEDA compliance maintained for Canadian customers if that market is served. Audit logs support compliance reporting. No PII stored in application logs. |
| Priority | High |
BR-07: Platform Reliability & Uptime
| Requirement | Detail |
|---|---|
| ID | BR-07 |
| Statement | Roundtrip must maintain a minimum 99.9% monthly uptime SLA for paying tenants, with planned maintenance windows communicated 48 hours in advance. |
| Rationale | Service businesses operate 7 days a week, including weekends and evenings. Dispatchers rely on Roundtrip to manage active jobs. Downtime directly impacts the tenant's revenue and creates a support burden for Traxs. |
| Success Criteria | 99.9% uptime = < 8.76 hours downtime per year. Monitored via external uptime monitoring (e.g., Better Uptime). Status page (status.roundtrip.app) updated in real time during incidents. P1 incident response within 15 minutes. |
| Priority | High |
07 — FINANCIAL MODEL
Financial Model
Pricing Tiers
| Tier | Monthly Price | Technician Seats | Key Included Features | Target Customer |
|---|---|---|---|---|
| Starter | $99/mo | Up to 3 | Tickets, clients, basic billing, standard routing | Solo or small 2–3 tech shops |
| Standard | $149/mo | Up to 10 | All Starter + AI route optimization, inventory, SMS notifications, reports | 5–10 tech businesses (primary ICP) |
| Professional | $249/mo | Up to 25 | All Standard + AI assistant, schema isolation, priority support, custom branding on invoices | 10–25 tech businesses |
| Enterprise | $399+/mo | Unlimited | All Professional + dedicated database, SSO, SLA, custom onboarding, API access | 25+ tech businesses, regulated sectors |
| Additional seats | $15/user/mo | — | Applies when seat count exceeds tier limit | Growth-stage businesses |
Revenue Projections
| Period | Tenants (Est.) | Blended ARPU | MRR | ARR | Notes |
|---|---|---|---|---|---|
| Month 6 | 50 | $130 | $6,500 | $78,000 | Soft launch, early adopter pricing |
| Month 12 | 200 | $145 | $29,000 | $348,000 | Word-of-mouth in target verticals |
| Month 18 | 600 | $155 | $93,000 | $1,116,000 | First marketing spend, trade shows |
| Month 24 | 1,500 | $165 | $247,500 | $2,970,000 | Referral program active |
| Month 30 | 2,800 | $170 | $476,000 | $5,712,000 | Channel partner program |
| Month 36 | 5,000 | $175 | $875,000 | $10,500,000 | Target scale — profitability threshold |
Unit Economics
| Metric | Target | Rationale |
|---|---|---|
| Customer Acquisition Cost (CAC) | < $300 | Primarily content marketing, trade community presence, and referrals. Low paid advertising dependency. |
| Lifetime Value (LTV) | > $3,500 | Based on 24-month average retention at $149 ARPU. LTV:CAC ratio > 11:1. |
| Monthly Churn Rate | < 1.5% | Sticky workflows (ticket history, client database, route data) create high switching cost. Target: < 1.5% monthly. |
| Gross Margin Target | > 75% | Infrastructure cost < $3/tenant/month at scale. Support cost reduced by self-service design. |
| Payback Period | < 3 months | At $149/month with $300 CAC, payback is 2 months — well within acceptable range. |
| Infrastructure Cost (1K tenants) | < $3/tenant/mo | Shared SQL Server, shared Redis, single API deployment. Hangfire runs on API host. Ollama on shared GPU server. |
Cost Structure
| Cost Category | Estimated Monthly (at 1,000 tenants) | Notes |
|---|---|---|
| Infrastructure (servers, DB, Redis, Keycloak) | $1,500–$2,500 | Scales sub-linearly with tenant count due to shared architecture |
| Ollama / GPU server | $400–$800 | Single GPU instance serves all tenants' local AI inference |
| SendGrid (email delivery) | $200–$400 | Based on estimated email volume |
| Twilio (SMS) | $300–$600 | Per-message cost; SMS volume tied to tenant notification settings |
| Domain, CDN, SSL (Cloudflare) | $50–$150 | Fixed cost, minimal scaling |
| Monitoring (Application Insights / Datadog) | $200–$400 | Scales with log/trace volume |
| Total Infrastructure | ~$2,650–$4,850/mo | ~$2.65–$4.85 per tenant at 1,000 tenants |
08 — GO-TO-MARKET STRATEGY
Go-to-Market Strategy
Target Customer Profile (ICP)
| Attribute | Ideal Customer Profile |
|---|---|
| Business Size | 5–15 technicians (sweet spot for Standard tier) |
| Industry | HVAC, plumbing, electrical, appliance repair, or IT service |
| Geography | United States (primary); Canada (secondary — served as foreign market from US entity); Australia (tertiary) |
| Tech Savvy | Owner or dispatcher is comfortable with smartphones; currently using at least one digital tool (even if it's just spreadsheets) |
| Pain Point | Losing time to manual scheduling, late invoices, technicians calling office for job info |
| Decision Maker | Business owner or operations manager — makes purchasing decisions unilaterally in businesses of this size |
| Willingness to Pay | $100–$250/month if the tool demonstrably saves time or money |
Acquisition Channels
| Channel | Strategy | Expected CAC | Timeline |
|---|---|---|---|
| Content marketing (SEO) | Blog posts targeting 'best HVAC software', 'plumber scheduling app' etc. Long-tail FSM keywords have high intent. | $50–$150 | 6–18 months |
| Trade community forums | Active participation in Reddit (r/HVAC, r/plumbing), Facebook Groups, and trade association forums. | $0–$50 | Immediate |
| Free trial (14-day, no CC) | Lower friction than paid-first. Converts well when the trial includes AI routing demo. | $100–$200 | At launch |
| Referral program | Existing tenants get 1 free month for each paying referral. High trust in trade communities. | $75–$150 | Month 6+ |
| Trade shows & associations | PHCC, ACCA (HVAC/Plumbing/Electrical) annual shows. Booth presence + sponsored content. | $200–$400 | Year 1+ |
| Channel partners | Accounting software integrations (QuickBooks, Xero) create referral pipelines once integration is built. | $100–$250 | Year 2+ |
Launch Milestones
| Milestone | Target Date | Success Criteria |
|---|---|---|
| Private Beta | Month 1–2 post MVP | 5–10 invited businesses using Roundtrip in production. Continuous feedback loop with dev team. |
| Public Beta (free trial) | Month 3 | 50+ trial signups. At least 20% conversion to paid within 30 days. |
| v1.0 General Availability | Month 4 | Full feature set live. Billing active. Support documentation complete. |
| First 100 paying tenants | Month 8 | Validated product-market fit in 2+ target verticals. |
| First 500 paying tenants | Month 14 | Marketing engine operational. Referral program driving measurable growth. |
| Nexus integration preview | Month 18 | Roundtrip ↔ Nexus CRM sync available to Professional+ tenants. |
09 — RISK REGISTER
Risk Register
| Risk ID | Risk Description | Likelihood | Impact | Mitigation Strategy |
|---|---|---|---|---|
| R-01 | Slower-than-expected adoption due to resistance to change in trade industries | Medium | High | Invest in onboarding UX. Offer white-glove setup for early adopters. Create vertical-specific demo environments (e.g., 'HVAC Demo Company'). |
| R-02 | Competitive response from established players (Jobber, Housecall Pro) adding AI features | High | Medium | Move fast on launch. Build switching-cost through tenant data depth (history, clients, inventory). Data sovereignty angle is hard for cloud-AI-first competitors to replicate quickly. |
| R-03 | Ollama / local LLM quality insufficient for route optimization | Low | Medium | Algorithmic fallback (OR-Tools) ready at launch. Monitor route quality in beta. Swap models as Ollama ecosystem improves. |
| R-04 | Infrastructure cost overrun at scale (Ollama GPU costs higher than projected) | Low | Medium | GPU server is a fixed cost shared across all tenants. Model inference can be batched. Fallback to algorithmic routing if GPU utilisation is too high. |
| R-05 | Security breach — cross-tenant data exposure | Low | Critical | EF Core Global Query Filter + SQL RLS (defence-in-depth). Automated cross-tenant penetration tests in CI. Regular third-party security audit before GA. |
| R-06 | Key developer attrition before launch | Medium | High | Comprehensive technical documentation (SAD, PRD, domain model) reduces bus-factor. Clean Architecture makes codebase navigable by new developers. |
| R-07 | Stripe (or payment processor) fee increase impacting margins | Low | Low | Abstract payment processor behind an interface. Can swap to Paddle, LemonSqueezy, or direct banking if needed. |
| R-08 | Twilio/SendGrid pricing increases impacting unit economics | Low | Medium | Both services are abstracted behind interfaces. Mailgun, Postmark, and Vonage are viable alternatives. Allow tenants to bring their own Twilio number. |
| R-09 | Regulatory change requiring data residency in specific countries | Low | High | Containerised architecture allows deployment in any region. Multi-region strategy documented but not implemented at v1.0. Enterprise tier can negotiate dedicated deployment. |
| R-10 | Scope creep delays MVP launch beyond viable market window | Medium | High | Strict MoSCoW prioritization in PRD. Should Have and Could Have features explicitly deferred. Weekly scope review against launch milestone. |
10 — SUCCESS METRICS & KPIS
Success Metrics & KPIs
Business KPIs
| Metric | Definition | Target (Month 12) | Target (Month 36) | Measurement |
|---|---|---|---|---|
| ARR | Annual Recurring Revenue | $350K | $10.5M | Stripe / billing system |
| Active Tenants | Tenants with at least 1 ticket created in last 30 days | 200 | 5,000 | Application DB |
| Monthly Churn | % of paying tenants who cancel per month | < 2.5% | < 1.5% | Billing system |
| Trial-to-Paid Conversion | % of trials converting to paid within 30 days | > 20% | > 30% | Billing system |
| LTV:CAC Ratio | Lifetime value divided by customer acquisition cost | > 5:1 | > 11:1 | Finance model |
| NPS (Net Promoter Score) | Would you recommend Roundtrip to a colleague? | > 40 | > 55 | Quarterly survey |
Product KPIs
| Metric | Definition | Target | Measurement |
|---|---|---|---|
| Daily Active Users (DAU) | Unique users who log in and perform an action daily | > 60% of active seats | Application analytics |
| Ticket Completion Rate | % of created tickets reaching Completed status | > 85% | Application DB aggregation |
| Route Optimization Usage | % of tenants running route optimization at least 3×/week | > 70% | Hangfire job logs |
| Mobile Technician Sessions | % of technician sessions from mobile device | > 80% | User-agent analytics |
| Invoice Same-Day Rate | % of completed tickets invoiced on the same day | > 50% | Application DB (ticket → invoice timestamp delta) |
| P95 API Response Time | 95th percentile API response time across all endpoints | < 200ms | Application Insights / OTel |
| Uptime | % of time platform is available and responding correctly | > 99.9% | External uptime monitor |
Operational KPIs
| Metric | Definition | Target | Measurement |
|---|---|---|---|
| Support Ticket Volume | Support tickets per 100 active tenants per month | < 5 | Support helpdesk (Intercom / Crisp) |
| Onboarding Time | Time from registration to first ticket created | < 10 minutes | Application event timestamps |
| Mean Time to Recovery (MTTR) | Average time to restore service after P1 incident | < 30 minutes | Incident management log |
| Infrastructure Cost / Tenant | Total monthly infra cost divided by active tenant count | < $5 (Month 12), < $3 (Month 36) | Cloud billing dashboard |
11 — ASSUMPTIONS & CONSTRAINTS
Assumptions & Constraints
Business Assumptions
- The field service SMB market will continue to digitise at the current pace; adoption is not reversing
- Trade business owners are willing to pay $99–$249/month for software that demonstrably saves time and improves cash flow
- Word-of-mouth in trade communities (Reddit, Facebook Groups, trade associations) is a viable low-cost acquisition channel
- A 14-day free trial with no credit card required is sufficient to convert the ICP without a lengthy sales cycle
- Local Ollama inference quality will continue to improve as the open-source model ecosystem matures
- The Traxs Company Nexus CRM integration will be available for joint marketing within 18 months of Roundtrip launch
Technical Constraints
- All AI inference must run on Traxs-controlled infrastructure — no external AI API calls with tenant data
- The initial deployment targets a single geographic region (US East); multi-region is a v2 consideration
- The platform must be operable by a small team (1–3 developers) without dedicated DevOps staff at launch
- Mobile experience is delivered as a PWA — no native iOS or Android app development at v1.0
- Payment processing must comply with PCI DSS; Roundtrip does not store card data — payment processing is handled entirely by Stripe or equivalent
Business Constraints
- Traxs Company is bootstrapped; no external investment. Infrastructure cost must be controlled tightly at launch.
- Legal and compliance review must be completed before General Availability launch
- Pricing must be competitive with Jobber and Housecall Pro while maintaining >70% gross margins
- Enterprise tenants with dedicated database requirements must be handled manually at launch; self-service Enterprise onboarding is a v2 feature
Roundtrip · Business Requirements Document v1.0 · A Traxs Company Product · March 2026