Skip to content
collins madu.
Collins Madu

Founder of Pycache

Full-Stack & AI Systems Engineer

Hiring an engineer?

Explore my experience

Have a project?

Discuss a build

Procurement and sales intelligence for wholesalers

Pycache is already used by multiple European beauty wholesalers.

Visit Pycache

Supplier offers and customer requests arrive in inconsistent Excel files, PDFs and emails. Buying and sales teams spend time cleaning that data, evaluating offers and matching supply to demand across spreadsheets and separate systems.

Capture and structure
Pycache automatically captures supported offers and requests from agreed inbox and file workflows, including Excel and PDF files and email attachments. It structures EANs, product references, descriptions, prices, currencies, quantities, minimum order quantities and availability, including stock versus preorder.
Compare and match
Compare each item with previous purchases, competing offers, sales history, customer demand and market references. Match available supply with existing customer requests.
Review and act
Buying and sales teams get dashboards, comparison tables, source evidence, recommended actions and exportable purchasing or sales sheets.

73 projects, nearly all built solo, end to end. Where a build was shared, the role line says what was mine.

Selected work

Browse the archive
Explore all work
How I work

From the first input to the handover.

Explore the stack
01

Understand

Start with the workflow: the inputs, the people and what breaks today.

Incoming formats
Supplier offersXLSX
Product catalogueCSV
Business rulesBRIEF
02

Architect

Make the data, decisions and boundaries explicit before building around them.

Decision model
offerscoredecision
BUYNEGOTIATEREVIEWIGNORE
03

Ship

Build the whole path, including the permissions and the ways it can fail.

Release checks
Authentication & roles
Audit trail
Deployment pipeline
04

Handover

Leave a system someone else can operate, with the documentation to match.

Ready for the next person
architecture.md
runbook.md
operator-sop.md
Working together

Something worth
building?

Tell me about the workflow, the team,
or the problem you keep working around.

Let’s talk
What do you charge?

€70 an hour as a baseline, covering architecture, backend, frontend, deployment and documentation. Where a project can be scoped properly up front, I prefer to quote a fixed price.

When could you start?

Usually within a week, sometimes the next day. The variable is how much research a project needs before I can scope it responsibly. Most engagements run four to twelve weeks; some become ongoing work.

Can you take over an existing codebase?

Regularly. Several projects here began as existing repositories. The case studies explain what I inherited, what I changed, and the role that was mine.

How do you handle confidential work?

Client systems are described by sector, never by name. I share the problem, my contribution and the stack without exposing client data or private source. Any permitted demo captures use invented data. The artwork here is conceptual.

What do I get at the end?

A deployed system, the repository, and documentation written for whoever runs it next: architecture notes, a runbook, and operator SOPs.