How small can an internal tool project be?

Very small. Some of the highest-return work we do is a focused two-to-four week build that replaces one recurring manual process.

Can the tool connect to systems we already use?

Yes. We integrate with CRMs, accounting software, spreadsheets, email and most services with an API, so data moves once instead of being retyped.

What happens if requirements change later?

The tools are built on a typed, documented stack so they can be extended. You own the code, and we offer ongoing support if you prefer us to handle changes.

Back to Portfolio

Custom Platforms/Tools

Content calendar

Content calendar is a internal tooling project from the Pixel2Tech tools practice. We were brought in because there was no audit trail, so when a number looked wrong nobody could tell when or why it changed. This page walks through the problem we were handed, how we approached it, and what changed as a result.

Brand: Content Calendar
Practice: Custom Platforms
Service: Tools
Year: 2025

The Work

What we designed for Content Calendar

Deliverables

Discovery
MVP build
Integrations
Docs & training

The challenge

When the project started, there was no audit trail, so when a number looked wrong nobody could tell when or why it changed.

Our approach

We connected the systems directly so the data moves once, automatically, with a record of each transfer.

The outcome

The process stopped depending on one person's memory.

Task time: −84%
Data entry errors: −82%
Users onboarded: 14

How we delivered this tools project

Step 01
Process discovery
We sat with the people doing the task, wrote down every step including the undocumented ones, and identified where errors and delays actually enter the process.
Step 02
Scope to one job
The tool was scoped deliberately narrowly — one job done properly — rather than a general platform that would need training before anyone could use it.
Step 03
Build with validation
Validation was placed at the point of entry so invalid data is refused rather than silently accepted, and change history was added so any number can be traced.
Step 04
Rollout and documentation
We rolled out to a small group first, adjusted from their feedback, then documented the tool so onboarding a new team member takes minutes.

Technologies and tools used

The stack below was chosen for this engagement because it matched the scale of the work, the team that would maintain it afterwards, and the performance the brief required.

React
TypeScript
Node.js
Supabase
PostgreSQL
Zod validation
Role-based access control

Why this project matters

Internal tools rarely get prioritised because they do not appear in revenue reports, yet they are often where the largest recoverable time cost sits. Removing a daily manual step returns hours every week for the life of the business.

If you are weighing up similar work, our services overview explains how we scope engagements, and about Pixel2Tech introduces the team who would run it.

Frequently asked questions

How small can an internal tool project be?: Very small. Some of the highest-return work we do is a focused two-to-four week build that replaces one recurring manual process.
Can the tool connect to systems we already use?: Yes. We integrate with CRMs, accounting software, spreadsheets, email and most services with an API, so data moves once instead of being retyped.
What happens if requirements change later?: The tools are built on a typed, documented stack so they can be extended. You own the code, and we offer ongoing support if you prefer us to handle changes.