10T Studios
← All articles

Blog

What to build first in an internal system

6 min read

Photo: T / Unsplash

Short answer

Build first whatever is retyped most often and touches money: usually a single record for a job or an order, from the first request to the basis for the invoice. Planning, reports and dashboards come after, on data you can trust. The exact order depends on the company, and below is the test that finds it.

01The test that decides the first step

Ask people in the company three things. What do you retype from one place to another? Where does something regularly slip — unbilled work, a forgotten quote, an unchased payment? And without which file would the company stop on Monday morning?

The answers tend to converge on one spot. That is where you start. If you note the hours spent retyping for two weeks, you also have a first number to count with.

02The order that works in practice

It is not a law, but most companies end up close to it.

  • 01One record instead of five: client, job or order in one place, with history. Without it there is nothing to plan or invoice.
  • 02The path to the invoice: hours, materials or delivered items turn into an invoice basis without retyping. This is where it most often turns out that less is invoiced than was done.
  • 03Statuses and alerts: everyone sees what state a job is in, and the system itself flags what is stuck or late.
  • 04Planning: only once there is true data on how long each kind of work takes.
  • 05Connections to accounting, stock or the online shop, if nobody is doing them by hand yet.
  • 06Reports: last, because a report is only as good as the data flowing into it.

03What can wait

Dashboards with charts, a mobile app for everyone, fine-grained permissions and automation of edge cases. They are not pointless; they just make sense once the core is running.

The temptation to build everything at once is strong, because the brief is written once and seems cheaper. It is paid for later: a large system launched in one go is mostly worked around, while a small one that replaced one specific irritation is used from day one.

04When the order does not apply

When the company has one acute pain, that is what gets solved. If enquiries arrive and nobody answers within two days, you do not start with job records; you start by making sure someone sees each enquiry and takes it.

And if some part works well in a ready-made service, leave it there. The first step of an internal system does not have to replace everything; it can be connecting what you already have.

Frequently asked

What should an internal system do first?
Whatever is retyped most often and touches money. Usually a single record for a job or an order, from request to invoice basis.
When should planning and reports be added?
Once the core runs and the data is true. Planning without data on how long work takes is guessing, and a report is only as good as its inputs.
Isn't it cheaper to build everything at once?
On paper, yes; in practice rarely. A large system launched in one go gets worked around, while a small one that replaced one specific irritation is used from the start.

Related

More articles