~/ mohit/consulting

Make Better Technical Decisions

Unclear architecture slows teams down. Guesswork turns into rework and complexity later. Happy to help you work through these choices.

Ways I can help

Thinking through problems together

Working through architecture, systems, and technical decisions when the path forward isn’t obvious.

Architecture Review

Identify bottlenecks, over-engineering, and hidden scaling risks

  • Identifying where your API layer is doing too much — and what to split.
  • Mapping out single-points-of-failure before they hit production.
  • Validating database schema choices for heavy read/write volumes.
  • Stripping out 'resume-driven' tech in favor of proven patterns.

Legacy Code Refactoring Strategy

Reduce tech debt without stopping feature delivery

  • Finding the 20% of tech debt that's causing 80% of the pain.
  • Untangling tightly coupled monoliths into logical domains.
  • Building integration test safety-nets prior to rewrite execution.
  • Creating step-by-step migration plans that don't halt shipping.

MVP & Tech Stack Strategy

Build what matters first — and avoid costly rewrites later

  • Choosing boring, battle-tested technologies over current hype.
  • Killing features that aren't hyper-critical to your initial launch.
  • Structuring the codebase to scale gracefully from day one.
  • Mapping out 3rd-party vendor locking risks early on.

Team Capability Building

Improve decision-making, not just code quality

  • Teaching systems-thinking using your actual repo, not toy examples.
  • Establishing practical CI/CD rules that don't block shipping.
  • Reviewing architectural decisions collectively as a team.
  • Developing pragmatic judgment around edge cases vs. over-engineering.

The Protocol

We start with the problem, look at the system, and work toward clarity.

01

Discovery Call

30 min

We talk through the problem, the system you’re working with, and where things feel unclear. No pitch, just a conversation to see if I’m the right person to help.

02

System Review & Direction

1-2 days

I take a look at your system, codebase, or requirements. Outline what’s going on, what matters, and possible paths forward, providing a clear direction with scope, timeline, and deliverables.

03

Engagement

Custom

We work together in a time-boxed way to address the problem — reviewing architecture, improving systems, or making specific technical decisions. The focus is on clarity and practical outcomes.

04

Delivery & Handoff

Final week

You walk away with clear decisions, documentation, and a practical path forward. The goal is to make sure that you and your team can move forward confidently.

Let’s talk it through

We can take some time to look at the problem together.