Roadmap
What we intend to build here, and what we are not promising yet.
This page is intent, not commitment. Nothing here has a date, and anything here may be dropped. It exists so you can tell the difference between not built and not planned.
Wanted, and blocked on us
Records through the API. Customers, jobs, quotes, invoices, timesheets and costs under
/api/v1, read first and then written. Until then, the MCP server reads and changes
most of them, and webhooks tell you when people, jobs, quotes and invoices
change.
More webhook events. Timesheets, costs, bookings and purchasing.
Considered, not committed
- A sandbox organisation with synthetic data, so nobody tests against live records.
- An OpenAPI description and generated clients, once the API is large enough to justify them.
- Redelivering a failed webhook by hand, and turning off an endpoint that keeps failing.
- Narrower MCP scopes than read and read and write, and a switch to turn connected apps off for an organisation.
Not planned
- Public access to the office workspace or the mobile apps. Both are organisation-private by design.
- Direct database or reporting access.
Something missing that would change what you could build? Tell us at hello@webhouse.com.au. The list above is ordered by what people ask for.