Case studies

Four businesses, and the systems they run on now.

Written for the owner, not the engineer: what was going wrong, what we built, what the owner was left with, and what changed, by how much. Clients are named by sector and city.

Furniture maker · 2 workshops · LudhianaMade-to-order manufacturing

Quote to dispatch on one workflow, confirmed from the floor.

Orders moved on paper from quote to dispatch, and nobody knew where one stood without walking the floor. We built one workflow from quote to dispatch, each stage confirmed on a phone, with every order on the owner's board.

The owner's board with every live order in both workshops in its current stage, ordered by promised date and with the one overdue order standing out, and a supervisor's phone in front of it confirming polish done on one order. — A drawing of the screen described here. Not a screenshot.

Before

Quote written by hand

Photographed onto WhatsApp

Paper job card carried to the workshop

Stage known by walking the floor

After

Quote raised on a screen

The accepted quote becomes the job

Each stage confirmed on a phone

Every order on the owner's board

Errors removed · Made-to-order manufacturing · Ludhiana

120 a weeknone

Job cards and dealer updates retyped by hand

documents typed a second time from a record that already held the same facts

Quote to dispatchdays from an accepted quote to the piece leaving the workshop, averaged over the month
Office time spent chasing order statustime at the desk answering where an order has reached, counted against the month before the build

Fashion brand · 11 stores · BengaluruD2C fashion retail

Eleven stores, three online channels, one set of numbers each morning.

Store, marketplace and website sales sat in three separate reports. Month-end took a week and the reports still disagreed. We built one place every channel reports into, a dashboard per store, and a reorder view that flags what to move, reorder or discount.

Yesterday across every channel on one dashboard: units sold, returns, each channel agreeing with its own report, a trend of units by channel, and the suggestions for what to move, discount or reorder. — A drawing of the screen described here. Not a screenshot.

Before

Three channels, three reports

Each with its own idea of a sale

Pasted into one sheet by hand

Month-end takes most of a week

After

Every channel reports into one place

One rule per number, written once

A dashboard for every store

Numbers ready before the shops open

Time returned · D2C fashion retail · Bengaluru

6 days1 morning

The month-end close

from the last day of trading to a set of numbers the owner will act on

Report lines that disagreed between channelssame day, same product, two sources, two answers
Lines out of stock at one store while another held thema size a customer asked for and did not get, while it sat unsold elsewhere

Research organisation · 40 sites · HyderabadClinical research

Forty sites entering patient data once, with every change logged.

Patient data arrived on paper forms and by email, and checking one record meant chasing three people. We built a platform where sites enter data once, checks run as it is entered, and every change carries who made it and why.

A vital signs form entered at the site, with checks raised as the values go in: a blood pressure outside its expected range, a date that cannot follow the visit date and a required answer left blank, beside the open query count and an audit trail of who changed what and when. — A drawing of the screen described here. Not a screenshot.

Before

Paper form filled at the bedside

Scanned, emailed, typed again

Corrections chased over email

The reason for a change in an inbox

After

The site enters the data once

Checks run as it is entered

Queries sit against their own field

Every change logged with its reason

Time returned · Clinical research · Hyderabad

11 days2 days

Query raised to query closed

from a monitor raising a query to the site resolving it

Data queries raised per 100 fields enteredfields a monitor sent back to a site for correction
Records with a gap in the audit traila change with no recorded author, reason or prior value

Residential developer · 9 projects · PuneReal estate

Every lead in one pipeline, from portal enquiry to booking.

Leads from portals, brokers and walk-ins landed in separate sheets, and follow-ups depended on whoever remembered. We built one pipeline for every lead source, with follow-ups assigned and reminded, and visits and bookings on one record.

One buyer's lead record: the portal, broker and site office enquiries merged onto it, the salesperson it was assigned to, the next step due with its reminder, the pipeline stage it has reached, and its journey from first enquiry to booking. — A drawing of the screen described here. Not a screenshot.

Before

Portal, broker and walk-in

Each in its own sheet or notepad

Follow-up depends on who remembers

Management asks and is not told

After

Every source into one pipeline

Duplicates caught as they arrive

Follow-ups assigned and reminded

Visit and booking on the first record

Demand converted · Real estate · Pune

45%96%

Leads with a logged first response inside a day

of every lead arriving from a portal, a broker or a walk-in

Leads that went cold with no follow-up loggedan enquiry that reached nobody and was never worked again
Site visit to booking paperworkfrom the visit a buyer decided on to a completed booking record

Start

Write a paragraph. A founder replies within one working day.

A 30-minute call with both founders follows. No deck and no proposal template, just a first read of whether we are the right shape for the problem.

Book the 30-minute call Write the paragraph

Or by email, phone or WhatsApp: hello@netogrit.com · +91 94330 54299 · WhatsApp (opens in new tab)