Roadmap
What is live, and what is next
Every capability on this site, with its real status. Live means you can use it today, and we list what it cannot do yet. Roadmap means it is planned in Service but not built. Via erp.io module means another live erp.io module does the job.
How to read this page
BIKE.co is the erp.io Service module. Service has a written plan: a list of capabilities matched row by row against established field-service software, and a sequence of build phases numbered from P0. This page translates where that plan stands into bike-shop terms, based on what is built and deployed in app.erp.io, not on what is drawn in a design file.
Three statuses appear here and on every product page. Live means built, with real screens and saved data, and deployed in app.erp.io now. Roadmap means planned in Service and not built, so you cannot use it yet. Via erp.io module means a different erp.io module, which is live today, does the job.
Live does not mean finished. For every live capability the table below also says what is not there yet, because a quote you cannot send to a customer is a different thing from a quote the customer approves by text. We do not publish ship dates for anything on the roadmap.
Every product capability
Each row is a page in the Product menu. For live rows, the last column is the honest list of gaps.
| Capability | Status | What works today | Not there yet |
|---|---|---|---|
| Repair quotes | Live | Numbered quotes with line items, optional lines, a % or $ discount and tax. Marked Sent, then Approved or Declined. An approved quote converts into a job, carrying the lines the customer chose. | Send only changes the status: nothing is emailed or texted, and there is no customer quote page, e-approval or PDF. No good/better/best tiers. No price book screen, so lines are typed in. |
| Work orders | Live | Numbered jobs with instructions and one or more visits, each with an assignee and a status from unscheduled to completed. A visit cannot close while a required checklist is unsubmitted. Jobs carry the quote lines and bill in one click. | No bench board by bike status (checked in, waiting on parts, ready for pickup). No intake tags or ticket printing. Jobs hang off a customer location, not a bike. |
| Scheduling | Live | A week view of visits by day, a just-mine filter, an unscheduled queue you book onto a day, reassigning the mechanic and moving the day, and a Today page for the crew. | No drag and drop. No time slots, hour grid or per-mechanic columns, and no bench-capacity limits. No recurring visits. |
| Service checklists | Live | Builder with 8 question types, immutable versions, auto-attach to every visit and required before it closes, fill on a phone including offline, per-submission PDF with photos and signature, CSV report, public link. | No starter templates ship: you build your own tune-up, safety and e-bike checks. |
| Technician time tracking | Live | Clock in and out against a visit or on its own, as work, drive, shop or break. Add forgotten shifts. A manager approves the week, and nobody approves their own hours. Overtime is calculated. | Hours do not flow onto invoices. No payroll export file yet. |
| Invoicing | Live | Bill this job creates a numbered invoice from the job lines once every visit is closed, with discount, tax, due date, terms and a message. Sent invoices are frozen and can be voided. | Send only changes the status: no email or text delivery, no invoice PDF and no customer invoice page. |
| Reporting | Live | Monthly visits closed, booked and unscheduled; invoiced, collected, outstanding and overdue; hours per person with the overtime split; the checklists report with CSV export. | No bench-throughput or comeback metrics, no margin (costs are not captured), no custom report builder and no charts. |
| Team & permissions | Live | Named capabilities with defaults taken from the erp.io workspace role, which maps to viewer, crew, admin or owner. Lead and manager levels exist but need a per-person grant. For example, crew can close visits and fill checklists but not schedule, and payments are admin-only. | No screen yet for granting an individual capability to one person; access follows erp.io roles. |
| AI receptionist | erp.iomodule | Phony answers the shop phone today as a separate erp.io module. | Phony cannot yet read Service jobs to answer is my bike ready, or book into Service. |
| Online repair booking | Roadmap | Requests can be entered into the requests inbox, and a checklist can be published as a public form. Public forms refuse submissions until spam protection is configured for the workspace. | Riders cannot pick a drop-off slot or see availability. There is no calendar booking. |
| Customer & bike records | Roadmap | Jobs, quotes and invoices are grouped under a customer location with a name and address. Customers belong in erp.io CRM. | No bike record: no serials, sizes, make and model, or per-bike repair history. |
| Mobile repair & routing | Roadmap | Visits at an address can be assigned to a person and a day. | No map, no route optimization, no stop ordering and no van stock. |
| Payments | Roadmap | An admin records money received against a sent invoice by hand, including partial payments; the invoice turns Paid when settled. | No Stripe, no pay links and no QR codes. The app takes no card payments. |
| Job costing | Roadmap | Hours are logged against jobs, and jobs have priced lines. | No screen compares labor and parts cost against price; no labor rates or parts costs. |
| "Your bike is ready" texts | Roadmap | Nothing customer-facing yet. | No text or email updates to customers of any kind. |
| Customer portal | Roadmap | Customers can fill in a public form. | No customer login, and no view of quotes, history or invoices. |
| Parts inventory | Roadmap | Parts appear only as typed lines on quotes and invoices. | No parts, stock or location model. |
| Purchase orders & reorder | Roadmap | Nothing yet. | Reorder points, purchase orders and receiving. |
| Accounting sync | Roadmap | Nothing yet. | Invoices do not post to erp.io Accounting or QuickBooks. |
Status as of September 30, 2026, from an audit of the deployed Service code. Live means available in a signed-in app.erp.io workspace.
Done by other erp.io modules
These are separate erp.io modules that are live today. Turn them on in the same workspace.
| Module | Status | What it does for a shop |
|---|---|---|
| Phony | erp.iomodule | AI receptionist and AI sales developer |
| CRM | erp.iomodule | Riders, fleet accounts and sponsors |
| Marketing | erp.iomodule | Campaigns, reviews, SEO and social |
| Client Portal | erp.iomodule | A branded space for each customer |
| Accounting | erp.iomodule | Books, invoicing and cash flow |
| CFO | erp.iomodule | Forecasts for the busy and quiet seasons |
| Pey | erp.iomodule | Payout reconciliation and supplier discounts |
| Sign | erp.iomodule | Waivers, rental and fleet agreements |
| Chat | erp.iomodule | Front counter to back bench, in threads |
| Projects | erp.iomodule | Custom builds, events and shop projects |
| ATS | erp.iomodule | Hiring mechanics before spring |
| Courses | erp.iomodule | Training new mechanics on your standards |
| PLM | erp.iomodule | Custom builds and parts bills of materials |
| Legal | erp.iomodule | Waivers, leases and warranty questions |
| Canvas | erp.iomodule | Planning the shop floor and the season |
The phases in plain words
Service is built in this order. Several phases are now partly built; here is where each one stands.
P0 and P1 - Decisions and foundation
Design decisions, sign-in through the erp.io shell, workspaces, roles, file storage and the test harness. Built.
P2 - Core records
Built: the requests inbox, customer locations, quotes with optional lines, and jobs with visits. Still to come: bike records with history, a price book screen, custom fields and an importer.
P3 - Checklists, permissions and embedding
The checklist builder, filling, PDF and CSV report, role-based permissions, public checklists and embedding. Built. A screen for per-person capability grants is still to come.
P4 - Scheduling and dispatch
Built: the week view, unscheduled queue and Today page. Still to come: drag and drop, time slots, bench capacity, arrival windows and route optimization.
P5 - Field app, web only
Built: the installable app with an offline queue for checklist answers, submissions and visit completion. Still to come: photo markup, web push and foreground check-in.
P6 - Time and job costing
Built: clock in and out, manual entries, weekly approval and overtime. Still to come: payroll export, expenses and job costing.
P7 - Invoicing and payments
Built: invoices from finished jobs and manual payment recording. Still to come: sending by email and text, PDFs, Stripe card payments, pay links and QR codes, refunds and posting to Accounting.
P8 - Inventory and fleet
Stock locations including vans, parts used on jobs, reorder points, purchase orders and receiving. Not started.
P9 - Messages, automation, reporting and API
Built: monthly reports. Still to come: ready texts and reminders, automation, deeper reports, a public API and the Phony booking tool.
The field app is web only, and what that rules out
The field app your mechanics and van techs carry is a web app only, and it is built. You install it from the browser to the home screen. When the signal drops, checklist answers, submissions and visit completions are queued on the phone and sent oldest first when it comes back, with repeated edits to one answer collapsed into one. It caches only the app shell, so offline you see an honest offline page rather than a stale list of jobs. It is new and has not yet been tested widely on real phones, so tell us how it behaves on the ones your shop uses.
Being web only rules some things out, and we would rather you hear it here. There will be no App Store or Google Play app. There is no Tap to Pay on the phone and no card-reader hardware, because both need a native app. Taking a card at the curb is planned as a Stripe payment link or QR code on the tech's screen, or typing the card in; today payments are recorded by hand. There is no Apple CarPlay or Android Auto, and no background GPS tracking of your staff.
Web push notifications and a foreground location check-in when a tech opens a job are still on the roadmap. On iPhones, web push will need the app added to the home screen, and uploads resume when the app is next opened.
Built and running
A technician clocked in against a visit on a job. Hours are approved weekly; they do not flow onto the invoice yet.
Illustration · sample data
Why checklists came first
Checklists were the first piece of Service to ship, before the rest of the chain. The reason is that the checklist is the hardest record to get right and the most painful one to lose. It carries photos, signatures and answers against a specific version of a template. If you change the tune-up template in March, the answers from last October must still read correctly. Service keeps template versions immutable for exactly that reason.
Now that jobs and visits exist, checklists attach to them. A template can be set to attach to every visit and be required, and the visit cannot be closed until it is submitted. For an e-bike, that makes the safety check before handover a gate rather than a good intention, and the signed PDF is something you can hand the rider.
If you want to see where things stand in person, start the free trial. Everything marked Live on this page is in the workspace you get.
FAQ
Questions shop owners ask
Can I send a quote or invoice to my customer from BIKE.co?+
Not yet. Marking a quote or invoice as sent changes its status, but nothing is emailed or texted and there is no PDF of either. Customer delivery is on the roadmap; for now you share the details yourself.
Will there be an iPhone or Android app?+
No, the field app is a web app only, and it is built. You install it from the browser to your home screen, and it queues checklist answers and visit completion offline. There will be no App Store or Play Store app.
Can I take card payments in BIKE.co?+
No, not today. Payments are recorded by hand against an invoice, including partial payments. Stripe payment links and QR codes are on the roadmap, and Tap to Pay is ruled out because it needs a native app.
What does Via erp.io module mean?+
It means another erp.io module that is live today does the job, and you turn it on in the same workspace. The AI receptionist is Phony, customer records sit in CRM, and the books sit in Accounting.
Do technician hours go onto the invoice?+
No, not yet. Hours are clocked against visits and approved weekly, and reports show them per person, but labor is not posted to invoice lines. You add labor to the quote or job lines yourself.
Can I use the roadmap features during the free trial?+
No, roadmap features are not built, so they are not in the trial either. The trial includes everything that is live, the whole request to invoice chain in Service and every other erp.io module, for 30 days with no card.
Keep reading
Take in your next repair on BIKE.co.
30 days free, no card, every erp.io module switched on. Start with a request, end with an invoice.