Build Sequencing
This page documents the rationale for the order in which Traxs products are built and released. Sequencing decisions are permanent in their consequences — the wrong order wastes months and misses market windows. The right order compounds advantages.
The Sequence
Phase 1 (Complete) Phase 2 (Now) Phase 3 (2027) Phase 4 (2027-2028)
────────────────── ────────────── ─────────────── ────────────────────
RoundTrip Waypoint v1 Relay v1 All three v2+
Live & marketing 5 core modules 4 core modules Expanding in parallel
July 2026 Q1-Q2 2027 Q2-Q3 2027 Ongoing
Why RoundTrip First
RoundTrip was built first because it has:
- The clearest ICP (trades businesses with field technicians)
- The strongest pain point (dispatch chaos, unbilled parts, late invoices)
- The fastest path to a paying customer (self-serve, 14-day trial)
- The most defined scope (field service management is a known category)
RoundTrip funds everything else. Its subscription revenue pays for Waypoint and Relay development. Without RoundTrip revenue, the rest of the portfolio cannot be built sustainably.
Why Waypoint Before Relay
This was a deliberate decision made in July 2026. The reasoning:
The cross-sell argument: RoundTrip customers are the primary early market for both products. A trades business owner using RoundTrip already has the pain that Waypoint solves — they can't see their business performance clearly, HR is a spreadsheet, documents are in a Dropbox folder. Waypoint is a natural "what's next" for an existing RoundTrip customer.
The data argument: Waypoint's Executive Dashboard pulls RoundTrip job data as its first killer feature. This integration story is immediately compelling — "open Waypoint and see your RoundTrip revenue, your team, your documents, all in one place." That's a day-one value proposition requiring zero data migration.
The Relay counter-argument: Copilot suggested Relay may have the stronger commercial opportunity because "businesses feel sales pain before operational pain." This is true for many businesses. However, for the trades industry specifically — RoundTrip's primary customer — the pain sequence is different. Trades businesses typically have more work than they can handle. Their pain is delivery and operations, not sales. Waypoint addresses their actual next pain point.
Relay benefits from waiting: Relay's power comes from integration with both RoundTrip AND Waypoint. A lead converted in Relay becomes a client in RoundTrip, and revenue flows into Waypoint. Without the other two products, Relay is just another CRM competing against HubSpot on features it can't win. With them, it's the front door to the entire Traxs ecosystem — a fundamentally different product.
What Gates Each Phase
| Gate | What It Unlocks |
|---|---|
| RoundTrip at 25+ paying customers | Validates market, funds Waypoint development |
| RoundTrip at 50+ paying customers | Funds first part-time developer hire |
| Waypoint v1 in private beta | Validates cross-sell motion, first suite customers |
| Waypoint v1 GA | Relay development begins with full resources |
| Combined 100+ customers | First full-time hire |
| $6K+ MRR | Pete and Robin take part-time salaries |
| $13K+ MRR | Full-time salaries viable |
The Module Release Strategy
Each product is built and released as modules rather than as a complete feature set. This is a deliberate commercial and engineering decision:
Commercial benefits:
- Each new module is a marketing moment — a reason to post, announce, and re-engage existing customers
- Customers can start with core value and expand — lower barrier to entry
- Feedback from early modules shapes later modules before they're built
- "What's new in Waypoint" keeps the product feeling alive and growing
Engineering benefits:
- Smaller scope per release means faster time to market
- Real customer feedback before building advanced features prevents wasted development
- Each module can be tested in isolation before the next begins
The pattern:
v1 — Core (ship fast, get customers)
v2 — Operations (build on validated foundation)
v3 — Intelligence (AI and analytics on top of rich data)
This pattern repeats for both Waypoint and Relay.
What We Are Not Building (Yet)
These are explicitly deferred — not forgotten, but not in scope until the foundation is validated:
| Feature | Deferred To | Rationale |
|---|---|---|
| Waypoint org charts | v2+ | Complex to build, low day-one value |
| Relay customer portal | v3 | Requires established customer base first |
| AI assistants (both products) | v3 | Need rich data before AI adds value |
| Compliance & Risk Management | Waypoint v3 | Niche requirement, limited SMB demand |
| Referral & Reputation Management | Relay v3 | Nice to have, not core to v1 value |
| Unified Communications Hub | Relay v3 | Significant infrastructure, deferred |
| Strategic Planning & OKRs | Waypoint v3 | Forward-looking, not day-one pain |
| Custom workflow engine | Waypoint v2 | Complex, builds on simpler modules first |
Timeline (Target)
| Milestone | Target Date |
|---|---|
| RoundTrip GA + marketing push | July 2026 ✅ |
| RoundTrip 25 paying customers | Q3 2026 |
| Waypoint planning & documentation | July-August 2026 |
| Waypoint v1 private beta | Q1 2027 |
| Waypoint v1 GA | Q2 2027 |
| Relay v1 private beta | Q2-Q3 2027 |
| Relay v1 GA | Q3-Q4 2027 |
| All three products in market | Q4 2027 |
| Combined $13K+ MRR | Q1-Q2 2028 |