WORK

Three problems, described the way the client described them

No logos we have not earned the right to show. What follows is the shape of real work — the before, what we built, and what we chose to leave alone.

See what it would cost
THREE PROJECTS

The same pattern, three industries

Client names are withheld until we have written permission to use them. Everything else — the volumes, the failure mode, what we built — is as it happened.

Warehouse racking full of stock

01Distribution

Orders that arrived as WhatsApp messages

Before

Around 120 orders a day landed as text, voice notes and photos of handwritten pads. Two people spent their mornings re-typing them, and the errors only surfaced when the truck came back.

After

The message is read, matched against the catalogue, priced and checked against stock. Anything ambiguous goes to a person with the original message attached instead of a guess.

BuiltDocument and message extraction · catalogue matching · stock check · exception queue

Clinician standing in a consulting room

02Health

Four locations that could not see each other

Before

Each site kept its own agenda and its own version of a patient. Moving an appointment meant a phone call, and nobody could answer "how did the group do this month" without a spreadsheet built by hand.

After

One system, one patient history, one calendar across every location — with per-site permissions so each team still only sees what it should.

BuiltSice rollout · patient history · multi-site agenda · role-based permissions · consolidated reporting

Accounting documents laid out on a desk

03Professional services

Documents that lived in an inbox

Before

Clients e-mailed documents and waited. Chasing what was missing was somebody's whole job, and every deadline arrived as a surprise.

After

Clients upload to a portal that reads, validates and files each document, chases what is missing on its own and only escalates the real problems.

BuiltClient portal · document reading and validation · automated chasing · deadline alerts

WHAT A CASE OF OURS CONTAINS

Four things a real case study has to say

If a portfolio only shows the finished screens, it is a design gallery. These are the four sections we insist on, on every project, whether or not it ends up on this page.

  1. 01

    The measured before

    How many, how long, who and what it costs when it goes wrong. Written down before anything is built, so "it feels faster" is not the success criterion.

  2. 02

    What we deliberately did not build

    Every project has a list of things we decided to leave manual. It is usually the most useful page in the document.

  3. 03

    The handover

    Repositories, data, documentation and a trained team. Written in a way that another agency could pick it up — which is the point.

  4. 04

    What happened after 90 days

    The honest number, including the parts that did not move. A case study without one is a brochure.

Dashboard with charts on a laptop screen
THE BIGGEST ONE

The largest project on this page is the one you are reading it on

Sice is nine modules sharing one database and one panel — organisation, CRM, sales, commerce, resources, accounting, projects, marketing and websites. Crack SRL runs its own clients, quotes, invoices and projects on it, and this site is published from its Websites module.

It is the honest answer to "can you actually build something this size?", and you can click through the whole thing before deciding whether to trust us with yours.

AN OPEN OFFER

Be the first named case on this page

If you are willing to have your project written up publicly — with real numbers, including the parts that did not work — we take 15% off the build and you get a case study you can use in your own sales. You approve every word before it goes up.

Send my project
FAQ

The fair questions about a page like this

  • Because we have not asked for permission to publish them yet, and inventing logos is the oldest trick in this industry. The scenarios above are real problems from real projects, described without anything that would identify the client. On a call we can talk about specific work and, where the client agrees, introduce you to them.

  • Yes — that is a fair thing to ask before spending money. Once a conversation is serious enough that it makes sense, we arrange an introduction to a client working on something comparable to what you need.

  • Each of the three above sits in a different bracket, and all three are quoted the same way: a free mapping call, then a written scope with the roles, the hours and a closed number per stage. Our rates are published, so you can do the arithmetic before you call.

YOUR TURN

Is your project the next one?

Every project on this page started the same way: one call about the real problem, not a demo of one more module. Yours can start the same way this week.

Get a written quote