Client
MITA Group
Unit
prodct [Labs] · + /skills
Duration
6 months · 2024
Shape
Concept-to-launch · cloud application
Headline
A cloud application for tender management — concept, design and shipment in six months. Built for the people who actually run tenders.
// prodct [Labs] case · MITA · 2024 · IT consultancy · cloud application

Tenders out of spreadsheets,
into a real application.

Tender management ran on shared drives, manual reminders and two heroic project managers holding it together. We built the application that replaced all of that — from blank page to production in six months.

24 wk
// concept → production launch
// on plan
1 app
// designed, built and shipped end-to-end
// not a prototype
Operator-first
// designed with the people who run tenders
// not for the demo
// 01 / the situation

Two project managers, fifteen tenders, a shared drive.

Every tender was a folder, a spreadsheet, a calendar invite and a memory. Two senior project managers carried the institutional knowledge — vacations were stressful events.

The mandate wasn’t to "digitalize tenders." It was to remove the single points of failure, end the spreadsheet sprawl and let the next hire be productive in week one.

  • 01

    Process lived in two heads.

    Onboarding was an apprenticeship.

  • 02

    Spreadsheet sprawl.

    No two tenders documented the same way.

  • 03

    Deadlines tracked by hand.

    A missed reminder was a lost tender.

// 02 / approach

Design with the operators. Ship to them.

Two-week discovery with the project managers, the bid writers and the partners who sign off. Process map first, screens second. Then a six-week MVP, then iterations against real tender cycles.

We didn’t build for the demo. We built for the Tuesday after launch — when a real tender deadline lands and someone needs to find the right contract clause in seconds.

  • A

    Discovery with the operators.

    Map the real process before designing the new one.

  • B

    MVP against a live tender.

    First release shipped during a real bid — not a sandbox.

  • C

    Iterate against actual cycles.

    Each tender cycle informed the next sprint.

// 03 / what we built

A tender platform that holds the institutional knowledge.

[Workflow]
Tender lifecycle workflow
Status, owners, deadlines, review gates — all in one place, no shared-drive folders.
[Documents]
Versioned document workspace
Clause library, version history, structured collaboration. The right answer is findable.
[Schedule]
Deadline & reminder engine
Automatic reminders, escalation paths, calendar sync. No more missed dates.
[Reporting]
Pipeline & win-rate reporting
Operational dashboards: where tenders stall, how long stages take, what we win and lose.
// 04 / outcomes

A platform they own. Knowledge that doesn’t walk out the door.

24 wk
// concept to live application
// shipped on plan
Day-1 onboarding
// new hires productive without an apprenticeship
// process in the system
0 spreadsheets
// active tenders no longer maintained on shared drives
// single source of truth
Operator-owned
// platform run day-to-day by MITA, not by us
// no dependency tax
// similar engagement?

Internal process living in spreadsheets? We turn that into a product.