Independent technology studio
Researching and building solutions for expensive, manual business workflows.
We study costly operational workflows and build focused software and automation around how the work is actually done.
The most expensive work in a business is usually the most ordinary.
Reconciling one record against another. Re-keying figures from a document into a spreadsheet, and from the spreadsheet into a system. Checking, chasing, correcting, filing twice. Work like this is repetitive, manual and rarely examined closely, because it has always been done this way and it always gets done.
It is also where operational cost, error and delay quietly accumulate. That is the work we build for.
On paper, a process is a line. In practice, it branches.
Examined closely, the same process runs across people, spreadsheets, documents and software. It carries manual checks, exceptions, reconciliations and repeated work that appear in no process document. Each branch is real work, and each one is a place where what is supposed to happen and what actually happens can part ways.
- People
- Spreadsheets
- Documents
- Software
- Manual checks
- Exceptionswhere the two part ways
- Reconciliations
- Repeated work
- Dashed line
- the process as documented
- Strands
- the work as performed
Somewhere inside that structure, expected behavior and actual behavior diverge. That is where the work starts.
Expected behavior, actual behavior.
Every workflow has two versions: the one described in the process document and the one performed on a Thursday afternoon with month-end approaching. Before anything is built, we trace the distance between them, with the records, spreadsheets, documents and exceptions as the evidence.
An illustration of a typical gap, not a specific client process.
As documented
- A record is created.
- The record is checked.
- The record is approved.
- The record is filed.
As performed
- A record is created in the system of record.
- Re-keyed into a spreadsheet so it can be checked.manual re-entry
- Checked by hand against a PDF and last month's export.manual check
- An exception is raised by email and waits for a reply.exception
- Corrected in the spreadsheet, then corrected again in the system.repeated work
- Approved.
- Filed in two places, because two teams need it.duplicate
Focused software and automation for the expensive parts of a workflow.
Every engagement starts with the workflow itself, not with a product. These are the kinds of problems we build for.
Reconciliation tooling
Software that compares records across systems and documents and surfaces the discrepancies, instead of a person doing it in a spreadsheet.
Document workflow automation
Automation for processes that depend on the repeated review, transfer, and verification of files.
Revenue leakage detection
Finding the operational gaps where billable work or expected revenue goes unnoticed.
Back-office automation
Removing the recurring manual steps inside routine administrative operations.
Cross-system verification
Checking that information agrees across the systems that hold it, continuously rather than by hand.
Focused workflow automation
Automating well-understood steps inside an operational process, with human review kept where judgment matters.
Understand the work before building the software.
Five stages, in order. Each one is a reason to stop if the work does not justify going further, and each one leaves you with something useful.
- 01
Problem
Identify repetitive, costly, or difficult operational work worth examining.
What you getA plain statement of the problem, who carries it, and what it costs in effort.
- 02
Workflow
Understand how the work is actually performed across people, documents, and systems.
What you getA map of the real workflow, exceptions and workarounds included, not the version in the process document.
- 03
Validation
Determine where existing tools fall short and whether solving the issue creates meaningful value.
What you getA clear go or no-go, with the reasons. If the answer is no, you keep the map and lose nothing.
- 04
Solution
Design a focused solution around the real workflow rather than assumptions.
What you getA narrow tool that fits the highest-value part of the work, tested against the workflow it came from.
- 05
Automation
Automate only the parts of the process where automation creates practical operational value.
What you getAutomation where it earns its place, and human review kept where judgment or accountability still matters.
Software is built only when the workflow justifies it.
- Does the problem repeat?
- Does it consume meaningful time or money?
- Are existing tools insufficient?
- Can improvement be measured?
If the answers do not hold, the useful outcome is a clearer understanding of the work, not another system to maintain.
The work becomes clear before anything is built.
Trace the branches, understand the evidence, and the path forward is usually narrower and simpler than the process it replaces. Sometimes it is software. Sometimes it is a better-understood workflow. Either way, it begins with a conversation.
An independent studio, deliberately close to the work.
Şivan Gatfar
Founder, Clear Branch Labs
Clear Branch Labs is an independent technology studio focused on identifying and solving costly operational workflows.
About the studio