Web Application  ·  Internal Tool Case Study

An internal tool that replaced spreadsheets,
Slack threads, and daily check-in calls

When a team grows past a certain size, coordination without the right tool becomes the bottleneck. Tasks get missed, statuses are unclear, and managers spend their time chasing updates instead of making decisions.

Category: Web Application
Delivery: 5–6 weeks
Stack: PHP · MySQL · JavaScript
Focus: Clarity & Team Coordination
Status: Delivered
Project management tool — team workflow and task tracking

What the client came with

A growing SMB had a team of 15 people running 8–12 concurrent projects. They were managing everything through a combination of spreadsheets, WhatsApp groups, and daily team calls. Tasks were duplicated, deadlines were missed, and the management team was spending hours each week just trying to understand what the current status was across the business.

Generic project management SaaS tools (Trello, Asana, Monday) had been tried and abandoned — they didn't match how this specific team worked, and the cost per seat was adding up. The ask: build something custom that fits the workflow, not the other way around.

Their words

"We tried three different tools. None of them worked the way we work. We need something built for how we actually do things — not something we have to change everything for."

SMB (15 team members) 8–12 Active Projects Mixed Team Roles SaaS Tool Fatigue Management Reporting Need

What we received — and what we built

We started with a detailed workflow interview to understand exactly how the team operated before writing a single line of code. The system was designed around their process — not a theoretical one.

What we received
  • Detailed workflow documentation from the team
  • List of roles and access levels needed
  • Current spreadsheet templates and reporting format
  • List of 12 "must-have" features from the management team
  • Server access for deployment
What we built
  • Project dashboard with status overview for all active projects
  • Task assignment with deadlines, priorities, and status tracking
  • Role-based access (admin, manager, team member)
  • Team activity feed — who did what and when
  • Management reporting view with project health indicators
  • Email notifications for assignments and deadline reminders

How we built a tool the team would actually use

The biggest risk with internal tools is building something that looks great but gets abandoned after a week. We mitigated that by designing the system around the team's existing habits — reducing friction rather than requiring behaviour change.

01
Week 1
Workflow Analysis

Mapped the actual workflow — not the ideal one. Conducted interviews with managers and team members separately to understand where the real friction points were and what information was genuinely missing.

02
Week 2
System Architecture

Designed the database schema and user role model. Defined the permission logic for admin, manager, and team member access before starting the build. Prototype reviewed and approved by the client.

03
Week 3–5
Core Build

Built the dashboard, task management, project tracking, activity feed, and reporting views. JavaScript used for real-time UI updates without page refreshes. Email notification system integrated.

04
Week 6
Team Rollout

Ran onboarding sessions with the team, migrated existing project data into the system, and handled first-week support. The tool was in daily active use by all 15 team members within 5 days of launch.

Before vs. after — what changed in how the team works

The team didn't get smarter or work harder. The system around them just stopped fighting them — and the results showed immediately in fewer missed deadlines and shorter management meetings.

Before
  • Project status lived in spreadsheets updated manually
  • Task assignments via WhatsApp — easy to miss or forget
  • Daily status calls consuming 45–60 minutes of team time
  • No visibility into who was doing what across the business
  • Deadline reminders done manually by managers
  • Management reporting required manual data collection each week
After
  • Real-time project dashboard — status visible to anyone at a glance
  • Task assignment with notifications — nothing falls through the cracks
  • Status calls reduced from 60 minutes to 15 minutes
  • Full team activity feed — who did what and when
  • Automated deadline reminders via email
  • Management reporting generated automatically from live data

A system the team uses — and management trusts

The tool went from zero to daily active use by the entire team within a week. The management team stopped spending time collecting status updates — they could see them in real time. Meetings got shorter, deadlines got hit more consistently, and the team stopped blaming "the tools" for coordination problems.

Project at a glance

5–6Weeks to launch
15Team members onboarded
3Role access levels
0Monthly SaaS fees
  • Real-time project dashboard replaced weekly manual status reports — management always knows what's happening
  • Task assignment and automated reminders reduced missed deadlines significantly in the first month
  • Daily status calls reduced by 75% — the tool answers the questions that used to require a meeting
  • Built exactly for how this team works — not adapted from a generic tool that almost fits
  • Full ownership — no per-seat fees, no dependency on a vendor's pricing decisions

Is your team managing projects in a way that works against them? A custom-built internal tool can change that. Let's talk about what yours would look like.

← Previous Restaurant & Café Website All Cases Next → Fitness Brand Identity