See the real problem
Not the symptom in the ticket. The business, the people, the risk, and what “done” must mean before any tool is named.
Technology & Solution Architect
I design the solution — not just the stack.
For leaders who need clarity before another tool, vendor, or rebuild. Quiet judgment. Paid consulting. Outcomes you can act on.
Does this sound familiar?
The technology was never the hard part.
Most teams I meet are not short of options. They are short of a clear decision. Cloud or on-prem. Build or buy. Fix the CRM or replace it. Ship faster — or stop the bleeding first.
I have spent my career on the inside of those rooms: architecture, infrastructure, products, operations, and the human side of delivery. What clients hire me for is not another slide deck of tools. They hire me for the judgment that sits between the business problem and the technical answer.
That is the work. Going beyond technology — to the solution that fits the life of the organisation you actually run.
“A good architect does not fall in love with the stack. They fall in love with the outcome — and stay honest about the cost of getting there.” Sujit Manke
How I work
From noise to a path you can trust.
Three movements. Same standard every time: understand the real constraint, design the solution, then choose the smallest honest next step.
Design the solution
Architecture as choices with consequences — what to build, buy, integrate, or refuse. Clear options. Named trade-offs.
Leave you able to move
A decision you can defend, a sequence you can fund, and — when you need hands — a clean handoff to delivery.
Selected problems
Stories, not a résumé.
A few shapes of work I return to. Details change by client. The pattern does not: clarity first, technology in service of the solution.
When the stack works — until it doesn’t
Systems that grew by accident. Ownership is unclear. The next outage will not be fixed by one more dashboard. We map the real dependencies and decide what deserves investment.
Full of data. Empty of follow-through
Leads, tickets, projects — captured everywhere, owned nowhere. The solution is rarely “buy another CRM.” It is the operating design that makes the next action inevitable.
Mail, cloud, and trust on the wire
Email that looks fine in a lab and fails in Outlook. Cloud that costs more than it returns. Security that is documented but not lived. Quiet, forensic work until the story on the wire matches the story on paper.
Technology decisions that feel personal
Founders and operators who carry the weight of every choice. A paid session is a thinking partnership: you leave with fewer open loops, not a longer backlog.
Consulting
Hours with someone who has sat in the problem.
This is not free advice and not a sales call. You book focused time. We work the decision in front of you. You leave with clarity you can use the same week.
Architecture Advisory
Paid consulting sessions for founders, CIOs, and operators who need a solution architect in the room — before they spend the next rupee of build or buy.
- Scoped sessions — by the hour or as a short block
- Written summary of decisions and next steps
- Honest call on what not to do
- Optional handoff to delivery when you are ready
When you need a team
PrecisionTech carries the build.
My personal practice is judgment and design. When the work needs a company — products, delivery, support, operations — that lives at precisiontech.in. The brands reinforce each other: clear thinking here, capable hands there.
Notes
Short writing. Slow thinking.
Articles will live here — small pieces on architecture, decisions, and the space between technology and the solution. A few titles to start the conversation:
If something here landed, that is usually the signal.
An honest consulting conversation — paid, focused, and useful whether we work together once or for years.
Later chapters may include immersive retreats alongside consulting. For now, the offer is clear: expertise, experience, and hours that move decisions.