Q3 Planning Draft
RelayOps Roadmap Review
RelayOps helps regional field-service teams coordinate dispatch, parts, invoices, and customer updates from one workspace.
Decision needed
Approve a focused Q3 plan instead of shipping every request.
Sales wants an enterprise story before the utility conference. Support wants fewer invoice questions. Operations wants a cleaner dispatcher workflow. The current draft puts every requested feature into the quarter so no stakeholder feels ignored, but it leaves the team without a credible delivery plan.
Commit
Role-Based Permissions
Add custom roles, field visibility, and admin policy controls for larger accounts.
- Why now
- Protects the enterprise story Sales needs before the utility conference.
- Scope guardrail
- Admin UI, policy engine, audit events, and migration only.
- Success signal
- Enterprise pilot can configure roles without engineering help.
Commit
Invoice Clarity Release
Replace the current invoice screen with clearer line items, tax details, attachments, and print styles.
- Why now
- Targets the billing questions Support keeps receiving from customers.
- Scope guardrail
- Prioritize comprehension and payment readiness over a broad visual redesign.
- Success signal
- Invoice-related support contacts fall by 20% after rollout.
Commit
Offline Technician Mode
Allow technicians to complete jobs, collect signatures, and capture photos when service is unavailable.
- Why now
- Gives field teams the mobile story they expected after last quarter.
- Scope guardrail
- Local storage, sync conflicts, photo queue, and status replay.
- Success signal
- Technicians can finish priority job flows without network coverage.
Recommended sequence
Plan the quarter around proof points, not stakeholder parity.
July
Enterprise and billing foundations
Start Role-Based Permissions and Invoice Clarity. Keep the Technician Heat Map to a dispatcher research spike before selecting a map vendor or mobile telemetry path.
August
Automation discovery and integration risk
Prototype Smart Follow-Up Rules with Customer Success. Validate QuickBooks sync edge cases, retries, mapping UI, and error queue before committing build capacity.
September
Field reliability and release hardening
Ship Offline Technician Mode and harden the committed releases. Keep Referral Credits and Customer Self-Service out of Q3 unless committed work lands early.
Scope calls
What changes from the current draft
Risks to manage
Credibility checks
- Permissions cannot slip if the enterprise deal is the primary Q3 proof point.
- Invoice work should solve the top billing complaints before expanding visual polish.
- Offline mode needs conflict handling, photo queue reliability, and clear release gates.
- Reporting demand should be met with temporary exports until product instrumentation is stronger.
Leadership review
Open decisions
- Confirm the three committed workstreams for Q3 delivery.
- Choose whether Heat Map, Smart Follow-Up Rules, or QuickBooks discovery gets first design capacity.
- Agree that Referral Credits and Customer Self-Service move to Q4 unless capacity opens.