What changed
We build eZacto for the engagements we actually run. When one of them will not fit the software, that is the next thing we fix.
Manage the team in a directory, sign in with GitHub, and let client contacts into the portal.
Invoice emails are delivered with confirmation, invoices carry attachments, and invoices are generated straight from tracked work.
The core workflows land: timesheet approval, invoice browsing and payments, expenses, client and project directories, and reports.
Turn tracked work into invoices, run eZacto in your own container, and let AI agents read your data through a read-only MCP server.
Imports from Harvest load from a verified snapshot, can resume safely, and reconcile three ways so every figure is accounted for.
The first usable eZacto: a documented REST API with scoped tokens, a responsive web app with the week grid, and secure sign-in.
The data model for clients, projects, time, rates and invoices is in place, and Harvest data can be synced incrementally.
eZacto was first deployed on Cloudflare Workers, alongside the tooling to snapshot a Harvest account.