Use cases
For freelance developers
You already have somewhere to track the code. What you do not have is somewhere the client can see progress, approve a staging build and pay an invoice without messaging you about it - which is most of the interruption in a freelance week.
The client-facing half, in one place
Projects, milestones as tasks, a progress bar the client can watch, and a portal where the invoices live. Your issue tracker stays where it is; this is the layer the client touches.
Staging builds and handover packs
New projects start with Staging Build and Handover Pack as deliverable sets. Credentials, documentation and the final handover go out through an access-checked route rather than a public link.
Scope creep, priced
Send a signed statement of work up front, then track hours against tasks. When the extra endpoint appears, the difference between the signed scope and the logged time is the invoice line - written down rather than argued.
Client-blocked work, visibly client-blocked
Mark tasks you are waiting on them for and they appear on the client's side. A project stalled on missing API credentials is stalled on missing API credentials, on the record, before the deadline conversation.
Common questions
- Is there an API?
- Not a public one today. Panorivo is the client-facing layer rather than something to integrate a pipeline with.
Every feature, in detail
Free for developers, and everyone else.
Every feature, unlimited clients and invoices, no card and no paid tier. Set up your first project in about five minutes.