Consultancy
Systems & process consultancy
A process nobody has mapped costs you twice: in the hours people spend working around it, and in software bought to fix the wrong problem. We map how your business actually runs and design the simplest system that stops the leak.
What we do
Systems & process consultancy is a structured review of how work moves through a business: who does what, in which tool, and where it stalls. We sit with the people doing the work, map the process as it really runs, and find the steps that cost the most time, money or errors. Then we design the simplest system that removes them. Sometimes that is new software. Sometimes it is a change to how a tool you already pay for is used.
Two Kazap engagements show what this looks like. For a London law firm, we moved requests out of email threads with 50+ recipients and into one portal that routes them to lawyers in 45+ countries; turnaround became two to three times faster, and the portal serves FTSE 100 and Nasdaq-listed clients. On a lease and licence platform, a sign-off between five and seven parties went from up to two weeks to two hours, once everyone agrees a time. That platform was trialled with two London landlords.
Some engagements stop at the plan, by design. For start-ups in materials delivery and volunteering, a hospitality business and a leading property developer, we delivered viability and competitor research, an architecture, a cost estimate and a mock-up of the first version in one to two months. Whether to build was their decision.
The method predates Kazap. Marcelo Neves, who founded Kazap in 2012, spent 2005 to 2007 at Banco do Brasil on a one-year programme that moved local-tax payments for 170 city councils and 510 branches from paper and post to a digital process. Errors fell by 30%, and turnaround went from 28 days to seven or fewer.
Data and reporting. Every engagement includes a data model and a database design, so the figures your reports depend on come from one place and add up. Where regulation applies, we design for it from the first diagram, with a working knowledge of UK, EU and Brazilian rules.
What you get
- A map of the process as it runs today, and as it should run
- A viability check and, for new products, a competitor review
- A system architecture and a data model
- A mock-up of the first version
- A cost estimate and a written recommendation, including when the answer is not to build
How it runs
- Understand the process. We interview and observe the people who do the work. Gate: you agree our description of the problem before we design anything.
- Test viability and cost. We check whether the fix is worth what it would cost. Gate: if it is not, we stop here and tell you.
- Design the system. Architecture, data model and a mock-up of the first version. Gate: you sign off the design.
- Estimate and decide. A cost estimate for building it. Gate: you decide to build, scale it down or park it. Nothing commits you to a build.
A review usually takes one to two months from first meeting to estimate.
Who it is not for
- Organisations that need a team of consultants on site at once. We are deliberately small, and you work with Marcelo directly.
- Anyone looking for a report to support a decision already made. If the analysis says do not build, that is what the report will say.
- If you already have a tested specification and only need it built, start with custom software.
Question
How long does a systems and process review take?
A systems and process review at Kazap Technologies usually takes one to two months. It ends with a map of how the process runs, a system architecture, a data model, a mock-up of the first version and a cost estimate. You then decide whether to build, scale it down or stop; nothing in the review commits you to a build.