Home/About
PracticeThe name is the work.
Constrange is a technology and business consultancy. We help organisations decide under constraint, complexity, change, and uncertainty — then turn that decision into a path operations can actually absorb.
Deepak Patil
Constrange
We started Constrange around a simple belief: better decisions begin with a clear understanding of the problem.
Technology has made it easier to build, buy and automate almost anything. It has also made it easier to move in the wrong direction faster.
We work with organisations when the answer is not obvious. We look at how the business operates, how systems and people interact, what constraints exist, and where the real trade-offs sit.
Then we determine what actually makes sense.
Build. Buy. Automate. Simplify. Or wait.
The goal is not to add more technology.
It is to bring clarity to the decision, make the reasoning defensible, and give the organisation a practical path forward.
01 The name
Constraint is not a limit we regret. It is the thing that makes a decision possible.
Constrange is constraint and range held in one word. The range is everything that could be done. The constraint is what makes most of it irrelevant. The work is to see both clearly enough that a path can be chosen.
Most organisations do not lack ideas. They lack a picture of the situation that is honest enough to rank those ideas. Tools arrive as catalogues. Programmes arrive as ambition. Meanwhile the actual work continues through unofficial paths, tired joins, and systems that will not move this year.
The name is a reminder we keep in view. A constraint that is unnamed still governs the work — it just governs it badly. A range that is unbounded is not freedom. It is noise. We name the constraint so the range can be used.
The mark follows the same logic: a ribbon that opens like a C, held by a bar. The ribbon is range. The bar is constraint. We do not decorate the work with it. We let it sit quietly, the way a good decision sits — visible, not loud.
02 Why this firm exists
Complexity without a named problem is expensive.
Constrange exists for the gap between a fluent answer and a decision that can live among real systems, real people, and a constraint that will not move.
Leadership is not short of information. It is short of judgement that has been held against the operating landscape. A model can list options. A vendor can narrate a future. Neither has sat with the unofficial process, the join that fails, or the team that cannot absorb another change this quarter.
We started the practice because that gap kept repeating. A platform is selected before the problem is named. An AI programme is funded because the category is fashionable. A transformation is announced, then spends a year searching for a use that will justify it. The organisation is not careless. It is overloaded. Possibility has outrun structure.
Constrange’s job is to restore the sequence: understand the situation, define the problem, then look at technology — including the option that no new technology is required. We are not here to query a model on your behalf. We are here to tell when the answer belongs to a different organisation. And when the same expensive constraint keeps appearing, and existing tools do not hold it, we may turn the solution into software. That is not how we start a conversation.
03 How we think
Hold the picture. Reduce the options. Leave a first move.
The method lives on its own page. What belongs here is the stance: context before tools, structure over catalogues, action as the last artefact.
We do not begin with a stack. We begin with the pressure as it actually is — work, systems, people, risk, and time, including the unofficial paths that keep the organisation running. Until those threads are in the same picture, more options only add noise.
Clarity is a reduction. It is a ranking made under constraint, with non-goals written down. A longer comparison sheet is not progress if every idea remains live. The useful question is not “what else could we do?” It is “what makes most of the other ideas irrelevant?”
A point of view is unfinished until it has an owner and a first move small enough to be real. Direction is always in scope. Build can sit with your team, a partner, or a mix. Either way the path has to be buildable.
- 01Context
A generic answer does not know your systems, your unofficial processes, or the cost of a wrong turn.
- 02Reduction
More options do not create clarity. A ranked path, with non-goals, does.
- 03Action
The last artefact is not a recommendation. It is a first move with a name next to it.
04 What we are not
A practice, not a playbook. Software when the problem has earned it.
Saying what Constrange is requires saying what it is not. The distinction is not branding. It is how we refuse to work — including when we build software.
Not an AI agency
We use models when they fit the problem. We do not sell a default intelligence layer, and we do not treat fluency as a decision.
Not a software-first vendor
We do not arrive with a platform looking for a problem to justify it. We start with the operating problem, the constraints around it, and the outcome that matters. When software is the right answer, we build or introduce only what earns its place in the system.
Not a body shop
We do not place anonymous capacity against an unnamed brief. The work is a held picture, then a path — not extra hands for a programme that has not been defined.
Not a sector playbook
Constraint is the landscape. We do not arrive with a template for your industry and a slide that already knows the answer.
05 How the work is delivered
Understand the system. Find the constraint. Change what matters.
The sequence does not change with the artefact. Consultancy, process change, automation, or software — each is a way the same reading can become action. None of them is assumed in advance.
Advisory
We work directly with an organisation. Situation, constraints, system, intervention, outcome. Sometimes the answer is not to buy anything. Sometimes it is to change a process, automate a join, or replace a system. Sometimes there is no technology problem at all.
Products
When a problem is recurring, important, and existing tools do not hold it, we may productize the answer. That software is the technology expression of the practice, not a second identity.
06 Brand language
A field, a bar, a path.
The illustrations on this page are Constrange’s own geometry — grain for the noise of options, a bar for the constraint that holds them, a continuing line for the decision. They are not decoration borrowed from a product company. They are how we picture the work.
Grain
The unofficial, the incomplete, the catalogue that will not rank itself.
The bar
A named constraint. Without it, the range is only noise.
The path
What continues after the reduction — owned, small enough to start.
A conversation
Bring the pressure as you currently see it.
You do not need a polished brief. If the next move is unclear, that is enough to start. We will help you find the problem underneath — and whether technology should wait.