Jump to a section10

Almost every company starts with a spreadsheet. It is free, everyone understands it and it changes in five seconds. The problem is not the spreadsheet itself, but the moment the company outgrew it and nobody noticed.

The signs you have outgrown the spreadsheet

  • There is “the good file”. Someone has to say which version is current, and two people have opened different copies at the same time.
  • Critical information lives in someone’s head. When that person is on holiday, the team visibly slows down.
  • Things get lost in handover. An order moves from sales to production through a message, and the message gets buried under fifty others.
  • You cannot answer simple questions quickly. “How many jobs are overdue?” takes ten minutes of filtering, not ten seconds.
  • Everyone sees everything. Including purchase prices or data not everyone should see.
  • Clients call to ask “is it ready?”. A sign that the system does not inform them by itself.

One of these signs is not enough. Three at once is.

What your own application solves

A single source of truth

Everyone sees the same information at the same moment, with no parallel copies. The status of a job is a fact, not an opinion.

Roles and permissions

Each person sees and edits exactly what belongs to their work. Enforced on the server, not merely hidden in the interface.

Your workflow, not a generic product’s workflow

An off-the-shelf CRM makes you move your processes onto its structure. An application built around your workflow does the opposite, and the difference shows in how fast the team adopts it.

Small automations with large effect

An email sent automatically to the client on completion, a notification when a job passes its deadline, a report that generates itself on Monday morning. Each saves a few minutes a day, several times a day.

When it is NOT worth it

To be clear, there are situations where the answer is “stay on the spreadsheet a while longer”:

  • The process changes monthly and has not settled yet. Automate chaos and you get automated chaos.
  • The team is two or three people working in the same room.
  • There is an off-the-shelf product covering 90% of the need at a small monthly cost, and the other 10% does not get in your way.

Your own system pays off when the process is stable, repetitive and costs time every single day.

What the move looks like

  1. Map the real workflow, not the one on the org chart: who does what, in what order, where it gets stuck.
  2. Pick the most painful slice and build only that. A system that solves one problem well gets adopted immediately.
  3. Import the existing data from the spreadsheets, so the team does not start from zero.
  4. Run both in parallel for a few weeks, until nobody opens the old file out of habit.
  5. Add the rest, one piece at a time, based on what the team asks for once they have used the system.

A concrete example

For a print shop I built an application where every order has a client, an owner, a deadline, specifications, materials with automatic calculation and a status visible to the whole team. Production moves through statuses, priority is set by dragging items in a ranked list or a calendar, and on completion the client is emailed automatically. You can see the project in the case study.

The question that actually matters

The right question is not “do I need a CRM?”, but “what does the way I work now cost me every month”. When the answer exceeds the cost of an application, the decision makes itself.

If you want to talk about your workflow, write to me.