Client requests in. Documents and invoices out.
- Forms
- Databases
- Time tracking
- Documents
- Sharing
- Invoices
Clients submit a request through a form you control. You track the time against it, then share a live view of the task and send the invoice, all from one record.
Sound familiar?
If you're running a dev shop, you've felt this.
Client requests arrive by email, DM, and phone, with no single place to catch them.
Every request gets written up by hand before anyone can start on it.
Time spent on small client requests goes untracked, so some of it never gets billed.
Proposals, scope docs, and reports get rebuilt from scratch every time.
One place for the client-facing work.
Clients submit a request, you track the time against it, and you share a live view of the task with the client. The documents and the invoice come from the same record.
- Share an intake form so clients submit a support or change request. The answers land as a record, already typed.
- Track time against each request, so the hours you spend are ready to bill.
- Share a live view of the task with the client, or assemble a proposal or report from a template.
- Log time and update records from inside Claude Code or Cursor, through the MCP server and the 61-tool API.
What a 10-person dev team pays.
Stop paying enterprise SaaS pricing for three tools that still don't integrate.
Built for how dev shops actually work.
One record holds the request, the time, the documents, and the invoice.
Client intake
Time tracking
Document assembly
Client sharing
One-click invoicing
From client request to invoice, in one place.
One flat price that covers the team, and you can cancel anytime.