Requests are scattered
Email, Slack and tickets. The same question gets lost between them.
ERP · Software development
ERP for software companies: clients, sprints, hours and invoices.
Code is in Git, tasks in Jira, hours in a spreadsheet, and the client asks in Slack. We bring this together so you see what is done, what it costs in hours and when to invoice.
What hurts
Familiar problems a custom ERP solves.
Hours show up at the end
The budget runs out halfway through the project and you find out at the end.
Invoicing by hand
Hours or milestones are copied into invoices on the last day of the month.
Support and new features in one list
The urgent fix and the nice-to-have compete for the same attention.
What the system looks like
Six modules connected in one flow.
Clients
Contract, contacts and everything agreed in one place.
Projects and sprints
Linked to Jira or Linear, readable for non-technical people.
Hours
Logged time against estimate, per project and per person.
Support
A separate queue for incidents with contract deadlines.
Invoices
Hours or milestones turn into an invoice with one click.
Capacity
Who is free for the next project and when.
The path of work
The same information from start to finish.
Data is entered once and moves forward. Nobody retypes it.
- 1Enquiry
- 2Estimate
- 3Contract
- 4Sprints
- 5Release
- 6Support
In practice
What it looks like inside.
We build on ready-made solutions such as Notion, Asana and monday.com. We do not write software from scratch; we organise and connect what already works well. The data on the screens is illustrative.
Notion · Asana · monday.com
Projects and sprints
Sprint progress and hours against estimate.
| Project | Sprint | Progress | Hours | Status |
|---|---|---|---|---|
| Client portal | Sprint 6 | 72% | 310 / 400 | In progress |
| Mobile app | Sprint 2 | 35% | 120 / 520 | In progress |
| API integration | Sprint 4 | 90% | 170 / 180 | In review |
| Support Q4 | Ongoing | — | 44 / 60 | In progress |
How we work
ERP does not have to mean heavy and expensive.
We use ready-made solutions such as Notion, Asana and monday.com and set them up around the way your company already works.
We map it
First we describe how work runs today: who does what, where people wait and where data is retyped.
We choose the base
We set up a ready-made solution you already use or one that fits your team, and connect it to your other programs.
We launch in stages
We start with one process, show a working result and add the rest once the team is used to it.
Questions
Frequently asked questions.
Should we drop Jira?
No. Jira stays for the developers. We connect it with the clients, hours and invoices that it does not cover.
Is it right for a product company?
Yes, but the focus differs: instead of hours per client we follow features, versions and support.
How long does it take?
We usually start with one process, for example hours to invoices, and add the rest in stages.
Related
Related pages.
Let’s look at how your company runs today.
A short conversation about what can be straightened out, connected and automated. The first conversation is free.