Solutions
Plan sprints or retainers, log time, and let clients file tickets against the same project.
In practice
Dev shops need a place for the build and a place for the aftermath. Felagar keeps cards, time, and tickets on the company so warranty work does not vanish into a mailbox.
After go-live, the client files a ticket. It lands on the project you already have, with time against the retainer instead of a mystery invoice line.
Engineering lives in one tracker, time in another, clients in email. Nobody can answer “is this in scope?” without a meeting.
Project views for the build, including Timeline when dates matter.
Time on people and projects, with weekly capacity on the agency side.
Tickets for clients that stay attached to the work, not a generic inbox.
Scope the project, track time as you go, then leave the door open for tickets.
Create the project and put milestones on the board or timeline.
Log time against the work as the team ships.
Share progress through the portal instead of status-email theatre.
Accept tickets after launch against the same company and retainer.
No. Keep git where it belongs. Felagar is the client-facing delivery, time, and ticket layer around the build.
Yes. The portal is not a dump of the whole studio. You choose the surfaces clients get.
Create an account, invite your team and clients, and you’re live, with no DevOps side quest. Updates, uptime, and the portal stay on us so you can stay on the work that pays.