Focused work
Issue and task timers, calendar context, outcome check-ins, async handoffs, and optional application or domain categories for desk and remote teams.
Software · agencies · distributed teams
Product in development · early access conversations open
xpressWorks is the workforce operations layer designed to connect planned work, approved time, labor cost, client billing, and accounting actuals—without turning visibility into surveillance.
Built for remote, hybrid, office, field, and shift teams in one system.
4role-aware work profiles
On clocklocation by policy
Versionedapprovals and corrections
Closed loopwith xpressBooks.ai
The xpressWorks difference
The signature is one traceable record from intent to result. Explore how planned work becomes an approved financial actual without losing the human, policy, or operational context in between.
Illustrative product workflow
Harbor Facilities · preventive service visit
01 · Planned work
Start with the customer, project, work order, task, shift, or outcome the work is meant to advance. Requirements, budget, site, and assignment travel with it.
Record trail
02 · Visible work
Workers start, stop, switch, and annotate work from desktop, web, mobile, kiosk, or crew clock. Offline records stay durable and sync without duplicate payable time.
Record trail
03 · Approved record
Managers review exceptions, notes, outcomes, expenses, and policy inputs. Every approval and adjustment creates a versioned record instead of silently rewriting history.
Record trail
04 · Financial readiness
Effective rates, labor burden, overtime inputs, billability, and accounting dimensions resolve against the approved version—ready for payroll and client billing review.
Record trail
05 · Accounting actual
Authorized source records can flow to accounting, then return invoice, payment, and profitability references. The next estimate learns from what actually happened.
Record trail
The Evidence Firewall
xpressWorks is designed to separate payable time, optional work evidence, and employment decisions. Teams get operational clarity while workers keep a visible, challengeable record of what the system collected.
“Off the clock” is a system state, not a suggestion.
Worker policy preview
This profile may collect
xpressWorks will not collect
Worker view: same underlying record, clear purpose, visible retention.
Disputes: challenge evidence without silently deleting payable time.
One system, four ways of working
A developer, service technician, shift supervisor, consultant, and accountant should not inherit the same crowded navigation. Work profiles change the daily surface and policy defaults without creating separate products.
Issue and task timers, calendar context, outcome check-ins, async handoffs, and optional application or domain categories for desk and remote teams.
Software · agencies · distributed teamsSchedules, attendance, breaks, overtime warnings, kiosk capture, leave, and visible exceptions for hourly teams.
Retail · hospitality · operationsJob sites, offline mobile capture, travel, mileage, crews, credentials, and on-clock geolocation with worker-visible policy.
Service · construction · mobile crewsBudgets, milestones, capacity, async handoffs, client approvals, billable rates, and profitability without forcing project teams into a shift UI.
Projects · consulting · client deliveryRemote, hybrid + office teams
xpressWorks gives knowledge teams one calm place to connect focused time to issues, tasks, deliverables, clients, and async handoffs. The story is the result—not how often someone moved a mouse.
Optional calendar, application, and domain context can support an outcome when policy allows it. Keystroke content and universal productivity scores are outside the product.

Software + IT
Connect estimates and focused time to issues, sprints, releases, incidents, documentation, and accepted technical outcomes.
Agencies + consulting
Keep client, project, phase, deliverable, billable time, approval, budget, and actual margin in one traceable operating record.
Operations + support
Plan time-zone coverage, cases, reconciliations, close tasks, service levels, handoffs, and workload without measuring presence.
Qualified Crew Planner
From a field visit to a remote project, xpressWorks is designed to recommend assignments from the full operating constraint set, explain every conflict, and leave the decision with a manager.
Assignment recommendation
Required EPA 608 · rooftop access · service vehicle
Window 9:00–11:00 AM · Fullerton, CA
| Candidate | Readiness | Travel | Workload |
|---|---|---|---|
| Amanda ChenRecommended | All requirements | 32 min | 6.4 h scheduled |
| Marco Ruiz | All requirements | 18 min | Overtime risk |
| Priya Shah | Credential expires soon | 41 min | 5.1 h scheduled |
Why Amanda: qualified, available inside the work window, no rest or overtime conflict, and the lowest schedule disruption after current assignments. Marco is closer, but the added hours would cross the configured overtime warning.
The Xpress advantage
Each product keeps its own tenant, database, credentials, runtime, and system-of-record boundary. Versioned contracts connect the work without hiding ownership or sharing application tables.
Workforce record
Time, schedule, attendance, approvals, expenses, labor readiness, outcomes, and workforce policy.
Service operations
Jobs, customers, sites, dispatch, work orders, and field-service execution remain authoritative here.
Financial actuals
Invoices, payments, ledger entries, taxes, and financial statements remain authoritative here.
Project delivery
Connected project and deliverable references can receive approved labor summaries without sharing infrastructure.
Complete product direction
The system is defined as a complete workforce operations platform, not a timer with a long roadmap. Production delivery will still advance in verified vertical slices.
Time + attendance
Desktop, web, mobile, kiosk, and crew capture; breaks, leave, corrections, approvals, offline sync, and versioned audit history.
Scheduling
Availability, time-zone coverage, credentials, skills, location, travel time, rest rules, overtime exposure, preferences, cost, and client requirements.
Field operations
Branded maps, address search, routes, travel-time matrices, offline map regions, and map matching around an authoritative on-clock record.
Payroll readiness
Effective rates, earning codes, overtime inputs, expenses, approval gates, provider acknowledgement, and per-record exception handling.
Billing + margin
Billable time, labor burden, cost dimensions, estimate-to-actual variance, client review, invoice references, payment status, and profitability.
AI + automation
Variance narratives, missing-data checks, schedule recommendations, and operational risk signals with source context and accountable human approval.
Integrations
Versioned Xpress contracts, public API, webhooks, dry-run imports, reversible mappings, idempotent retry, health dashboards, and full tenant export.
Governance
Tenant isolation, SSO and SCIM direction, custom roles, audit export, retention controls, regional policy packs, and accessible role-adaptive navigation.
A different operating question
| Operational question | Typical time-tracker boundary | xpressWorks product direction |
|---|---|---|
| What did the hours produce? | Often left in a separate task or project tool | Outcome, acceptance, effort, cost, and variance stay linked |
| What may be collected? | Policy can feel distant from the worker’s daily flow | Active policy and collected data stay visible to the worker |
| What happens after approval? | Export time or create an invoice | Reconcile labor cost, billing, payment, and the next estimate |
| Who should take this work? | Availability and schedule fit | Skills, credentials, time zone, route, rest, leave, cost, and preferences |
| How does field data behave offline? | Varies by device and workflow | Durable local capture with visible pending and conflict states |
Straight answers
The direction is ambitious, but the boundaries are deliberate. These are the questions we expect responsible buyers and workers to ask first.
xpressWorks is in product development. This site describes the complete product direction, and early-access conversations are open for organizations that want to help shape the first production deployments.
No. Evidence capture is designed to be off by default. Organizations deliberately configure disclosed policies, workers can see what is active and what was collected, and payable time remains separate from optional evidence.
Yes. Focused and project work profiles are designed for software, IT, agencies, consulting, support, and business-operations teams. They connect time to issues, tasks, milestones, client work, and outcomes without treating mouse movement or online presence as the work itself.
Mapbox is the selected mapping and location-intelligence platform for maps, geocoding, routes, travel-time matrices, map matching, and offline map context. xpressWorks and PostGIS remain authoritative for on-clock policy, geofences, time, and location records.
No. xpressWorks prepares and governs workforce records. xpressBooks.ai remains authoritative for invoices, payments, ledger entries, taxes, and financial statements; payroll providers remain authoritative for payroll processing and tax filing.
Early access
We are looking for field, shift, project, and distributed teams —including software and knowledge-work teams—willing to pressure-test work profiles, privacy policy, qualified scheduling, Mapbox field workflows, and the xpressBooks.ai reconciliation loop.
Conversation brief
Request received
Our team will review the workflow and follow up by email.
Reference RECEIVED