One page per customer
Jobs, invoices, payment behaviour, documents, agreements. Only what was agreed, with as little extra upkeep as possible.
Practice / A customer page, not a CRM
A customer page, not a CRM
Most CRM systems are built for structured sales processes. Most businesses need something else: one page that says what has happened with this customer.
The starting point
The work
in between.
- Master records often sit in the books, quotes in the quotes folder, emails in the mailbox, and single agreements only in notes or in memory.
- Existing systems can be connected over approved, monitored access. Where current sources, rights or upkeep are missing, the state is still known mainly by whoever last looked after the account.
- A CRM was introduced once and is kept up by two people, one of whom has left.
- Every call starts with a request to hold on while someone searches.
A suitable design
What needs to
work together.
These components describe one possible individual scope. Scope and rules are agreed with your business.
The picture comes out of the work
Connected information appears from the live cases. Anything unclear or not connected still has to be recorded deliberately.
Patterns, not scores
The system says what is different from usual. What that means, you know better.
An example decision card
A regular customer has not ordered for eight months
Before that a job came in about every ten weeks. The last invoice was paid late.
There can be many reasons for that. It is a note, not a diagnosis.
How does the note come about?
- previous gap between jobs: around 10 weeks
- current gap: 34 weeks
- no open complaint recorded
- → notable against the pattern of this customer
07 · To look up
One customer. One page.
Pick an invented customer. The state, the work, the invoice, the contacts and the documents change. The structure stays the same.
Customer page for Example business, metalwork is shown.
Customer page · Monday 08:12
Example business, metalwork
Example customer since 2019 · western region
What matters now
One invoice has been due for six days. The open quote has been waiting for a reply for nine days.
2
cases open
one job, one quote
€4,860
invoice open
due for 6 days
9 days
since last contact
the quote is with them
Jobs and quotes
- Handrail, north wingSigned off in full · invoice open
- Escape stair, works hallQuote sent · reply open
- Gate guide, store 2Finished · 14 May
Open invoice
- Number
- R-2026-184
- Amount
- €4,860
- Due
- 30 July 2026
Open. A friendly reminder is prepared but not sent.
Recent contact
- Email Quote for the escape stair sent, with two possible builds.
- Phone Handrail signed off without reservation.
- Note Access for the platform lift only possible until 3 pm.
Documents
- Quote, escape stairPDF · version that applies · 27 July
- Sign-off, handrailPDF · signed · 22 July
- Photo record18 photos · handrail job
How does that state come about?
- Invoice R-2026-184 has been due for six days under its payment term.
- For the same company there is no complaint and no separate agreement on record.
- The quote of 27 July was delivered; there has been no contact since.
- That produces two visible notes, and no rating of the customer.
An illustration. The names are generic example businesses; cases, amounts and contacts are invented. There is no rating, no score and no hidden profile data.
The picture comes out of the work
The job, the invoice, the contact and the document are not entered again for this page. They appear here because they arose in the case anyway.
A note is not a diagnosis
The page shows what is different or open. Why that is and what follows from it is still decided by the person who knows the customer.
The countercheck
Where things
can go wrong.
As soon as a customer page starts rating people, with traffic lights, scores or probabilities, it becomes a tool nobody trusts any more. And depending on what is stored, data protection duties follow. Both argue for staying deliberately narrow here.
A useful first trial includes this failure case explicitly. Fast processing alone is not success if checking and correction create more work.
The connection to the next task
Your first stage
Start where
the work improves.
For A customer page, not a CRM, we choose a bounded first outcome with your team. Existing specialist systems can stay where they fulfil necessary requirements. We compare time relief, payments that can end and the cost of the new way of working.
The workshop gives you priorities and a roadmap. You can continue internally or with support from Markus Kirchmair. The choice of model and agent follows the task, with data and rules retained outside an individual chat.
Explore the workshop →Ready for the next change
Keep the work simple.
The first view should show the next relevant decision. Reasoning and sources remain accessible. We leave out unnecessary features and make actual progress visible.
When a rule changes, agents can help investigate the impact, prepare the adjustment and update tests and documentation. A qualified person assesses the result and its adoption.
Try a change →Your first step
Say yes
to less.
Less unnecessary software. More room for your work. Let’s find the useful first step.