Skip to content

Mrigankar Sonowal: I turn complex processes into practical software.

--:-- IST · Pune, India

scroll

Control room

Everything at a glance

MS --:--

Hello: I’m Mrigankar
Process automation + custom ERP
for teams that outgrew Excel ✦

Mrigankar Sonowal

Status

Taking projects

Builds for

Every screen they work on

  • Web apps
  • Windows
  • macOS
  • Android
  • iOS

Education

  • MBA · Business AnalyticsIIM Amritsar · Class of 2026
  • B.Tech · Computer ScienceLovely Professional University · 2024

Stages, gates, Roles, evidence, Approvals, follow-ups, Reports, visibility

The idea

Every business already runs a system. It lives in spreadsheets, chats and memory. I find it, name its stages, put gates where decisions happen, and turn it into software people trust.

Here to get something built, or to hire? Pick one and the page puts what matters to you first.

Who are you here as?

Selected work · freelance

Three businesses, three systems.

Each one designed from how the client’s work actually moves, and built end to end, from requirements to deployment. Real screens, fictional data.

  1. In daily useWeb application

    Evidence-based Sales CRM

    RelayCRM

    Connects lead capture, review, assignment and sales execution, where deals move only on evidence.

    relay.mrigankar.com
    Relay CRM: Evidence-based Sales CRM, demo screen
    Blocked · a scheduled call does not count
    Call logged · follow-up created
  2. In deliveryWindows applicationWeb admin portal

    Road Tender Estimating Software

    RateAnalysis

    Converts a road tender’s bill of quantities into item-level execution cost estimates.

    Rate Analysis: Road Tender Estimating Software, demo screen
    BOQ line classified · rate set
    Rate analysis · locked in demo

How a project runs

Five stages. Two gates.

The full approach
  1. 01

    Discover

    How does work actually move today?

    I sit with the people doing the work: who hands what to whom, where decisions happen, what gets re-typed, and what everyone waits on.

  2. 02

    Map

    What should the system enforce?

    The process becomes stages, gates and roles, along with the rules the software will hold so people don’t have to remember them.

    Gate · your sign-off

  3. 03

    Build

    Does it fit the way people work?

    Short cycles with working screens early. Feedback comes from using the software, not from reading a document about it.

  4. 04

    Deploy

    Is it safe to depend on?

    Cloud or on-premise deployment, access control, backups and licensing where it applies. Data is migrated from the old sheets.

    Gate · your sign-off

  5. 05

    Hand over

    Can the team run it without me?

    Training by role, plain-language guides, and a period of support while the new way of working settles in.

Guided missions

Don’t take my word for it.Try to break the rules.

Your progress

0/11

Each mission takes about a minute. It signs you in to the right seat, and you watch for the moment the system steps in.

Forge PMS

MISSION 01

~1 min

Hit the approval gate

Seat: Daniel · Project Manager

  1. 1.Open any project and switch to the Board tab.
  2. 2.Drag a part from Quotation towards Order.
  3. 3.Watch where it lands.

Look for: The part waits for approval instead of moving. An approval request appears for the right people.

Relay CRM

MISSION 01

~1 min

Try to cheat the pipeline

Seat: Priya · Key Account Executive

  1. 1.Open Pipeline.
  2. 2.Move a “New lead” company straight to Contacted.

Look for: Blocked: a scheduled call does not count. Skipping a stage is refused too.

Rate Analysis

MISSION 01

~1 min

Classify a BOQ

Seat: Estimator

  1. 1.Filter to unclassified lines.
  2. 2.Assign a rate to one.
  3. 3.Check the Issues tab.

Look for: The line flips to rate-set and the issue count drops.

More in each case file: Forge PMS · Relay CRM · Rate Analysis

Delivery discipline

How your project is kept on track.

From a project in delivery right now. Every decision is written down, every question gets an answer, and nothing outside the agreed scope is built without a price and your approval.

decisions logged, each with its reason
211
client questions logged and tracked
147
staged milestones, each with an acceptance checklist
4
automated test files
200+

The signed agreement is the scope. Anything beyond it is priced and approved in writing before it is built.

Client dependencies that could move a date are tracked against the milestones, so a slip is seen early instead of explained late.

How a project runs, step by step

Confidentiality

What you see is real software.What you don’t is on purpose.

client: Excluded: client identity

stage_names: Excluded: confidential workflow

rate_formula: Excluded: proprietary calculation

build: leak-check passed ✓

Demos use fictional data and placeholder branding. Every build fails if a word from the real system appears in its source. That is how carefully your processes would be kept too.

How the demos are kept clean

Let’s mapyour process.

Four questions, two minutes, and a first sketch of the system your work could run on.

Hiring? Read my résumé