CASE STUDY

Example buildWeb App

Business Automation Dashboard

Replaces daily spreadsheet work with automated reports, alerts and role-based access.

Type
Scheduled jobs + dashboard
Build time
About 6 weeks
Platforms
Browser, alerts to email or chat
Starts at
₹20,000*

This is an example build. HumansOfCoding is a new studio with no client work to show yet. This page describes how the project would be scoped and built — the same thinking you would get on a real one. Nothing here is a past client, and no number on this page is a result.

THE SITUATION

What's actually broken.

Someone spends the first two hours of every working day exporting files, pasting them into a master spreadsheet, fixing what did not line up, and emailing the result to six people. That file has become load-bearing, and exactly one person understands it.

This is the most common software problem in a growing business, and the most under-rated one to fix. It is not glamorous. It buys back roughly five hundred hours a year and removes a single point of failure.

  • Two hours a day spent exporting and pasting

  • One person understands the master file

  • Six people read yesterday's numbers, not today's

  • Everyone sees everything, including margins

VERSION ONE

What we'd build first.

Every item here earns its place by being something a real user would miss on day one.

Pull instead of paste

Scheduled jobs that fetch from the source systems directly — an API, a database, an SFTP drop, or a mailbox that receives a daily CSV.

The rules, written down

Every fix that currently happens by hand becomes an explicit, tested transformation. The ones that cannot be pinned down get flagged for a human rather than silently guessed.

The dashboard

The numbers those six people actually read, live, instead of as yesterday's attachment.

Alerts

A message when a number crosses a threshold or when a source fails to arrive. Silence should mean everything is fine.

Role-based access

Finance sees margins, the floor sees volumes. Right now the spreadsheet shows everyone everything.

DELIBERATELY NOT IN V1

What we'd leave out.

Not because these are bad ideas. Because each one is designed better once the first version has told you something.

  • Predictive analytics and forecasting. Get the reporting trustworthy first; a forecast on top of shaky data is worse than no forecast.
  • Replacing the source systems themselves.
  • A mobile app. Alerts go to email or WhatsApp; the dashboard is responsive and that covers the phone case.

UNDER THE HOOD

How it's put together.

Scheduled jobs
Python, which is the right tool for pulling and reshaping messy data
Storage
Postgres, with the raw pulls kept alongside the cleaned output so any number can be traced back
Dashboard
React with a charting library
Alerts
Email plus a WhatsApp or Slack webhook
Hosting
One small cloud instance and a scheduler

HOW IT RUNS

Week by week.

  1. 01

    Week 1

    Sit with whoever owns the spreadsheet and write down every manual step. This week matters more than the rest.

  2. 02

    Weeks 2–3

    Data pulls and the transformation rules, checked against the last three months of the existing file.

  3. 03

    Weeks 4–5

    Dashboard, roles and alerts.

  4. 04

    Week 6

    Both systems run in parallel and the numbers are compared daily until they match.

BEFORE YOU START

Worth knowing.

Running both the old spreadsheet and the new system side by side for a couple of weeks is not wasted time. It is the only way to prove the new numbers are right before anyone trusts them.

MVPs start at ₹20,000*. Final pricing depends on features and project scope. Third-party costs — cloud hosting, domains, external libraries, APIs, app-store fees and any other paid service — are billed separately and are not included.

Want this built for your business?

Tell us what you're thinking. We'll figure out the next step together.

Free 20-min idea call · No obligation

Book a Free Call