Business software engineer

I build software that removes operational bottlenecks.

Businesses lose time because information is scattered across WhatsApp, spreadsheets, notebooks and disconnected tools. I build systems that organize information, automate repetitive work and provide operational visibility.

View Solutions Book Discovery Call

Independent engineer. Building reliable systems for retail, logistics and service businesses.

Problems I Solve

The cost isn't one big failure. It's a thousand small ones.

Every re-typed order, every lost document and every forgotten task quietly drains time and money. These are the patterns I see in almost every business that comes to me.

Information is scattered

Orders, leads, inventory and customer data live in different places — WhatsApp chats, spreadsheets, notebooks and tools that don't talk to each other.

Repetitive work

Staff spend hours manually copying data between systems, re-entering details, retyping the same information into different places.

No operational visibility

A business owner can't see what's happening across the business — what's pending, what's late, what moved today, where the bottlenecks are.

Follow-ups slip through

Important tasks depend on memory. Orders get delayed, leads go cold and commitments are forgotten because nothing tracks them.

Business Systems

Practical systems, built around how your business actually runs.

Each system is designed around a specific operation — not a template. The measure of success is the same in every case: the business runs smoother.

Retail Operations System

Inventory tracking, ordering, offline support and staff management.

One source of truth for stock, sales and staff — on every device, even when the internet drops.

Client Management Portal

Project tracking, communication and document sharing.

Clients always know what's happening. Fewer status calls, fewer surprise questions.

Opportunity Discovery Platform

Aggregates and ranks opportunities automatically.

The team sees the best prospects first, scored and sorted without manual sifting.

Custom Workflow Automation

Connects existing processes and reduces manual work.

Data moves itself. Staff stop retyping, and nothing falls through the cracks.

How I Work

Understand first, then build.

I don't start with a solution. I start with the people doing the work and the process they live with every day.

1
Understand the workflow
We trace how work actually happens today — the tools, the hand-offs and the shortcuts people have invented.
2
Identify bottlenecks
We find the steps that cost the most time and the ones people quietly avoid doing.
3
Design the system
A plan that fixes the real problems, simple enough that the team will actually use it.
4
Build and deploy
Delivered in working stages, so the business keeps running while we build.
5
Support and iterate
Real usage surfaces what to improve. We keep the system sharp after launch.

Case Studies

Worked examples, not a gallery of technologies.

Every engagement follows the same shape: understand the mess, fix the underlying process, and let the software carry it.

01Retail · Multi-location

A multi-store retailer stopped losing track of stock.

Three locations, one warehouse, and no way to know what was actually in stock on any given morning.

The problem

Stock counts were trusted until they were wrong. The owner discovered what was really moving only when the month-end spreadsheet finally came together.

How it worked before

Each store kept its own spreadsheet. Orders came in over WhatsApp, and a manager re-keyed everything into a shared file at the end of the week.

The solution

A single inventory and ordering system used by every store and the warehouse together. It works offline, flags low stock automatically, and records every movement once.

Results

Weekly stock reconciliation went from a full day to under an hour. The owner now opens a screen, not a question, to see what's available where.

02Client services

A service business stopped losing follow-ups between teams.

Client requests arrived in three different channels, and everyone assumed someone else had handled them.

The problem

There was no single place to see what was open, what was overdue, and who was responsible. Tasks depended on memory and on asking around.

How it worked before

Requests were logged in notebooks and message threads. Status was chased by follow-up messages, and documents were emailed back and forth.

The solution

A client portal where every request is logged, tracked, and visible to both the team and the client. Common requests are turned into automated checklists.

Results

Nothing gets lost in an inbox anymore. Clients see progress without asking, and overdue items are surfaced before anyone has to remember them.

Capabilities

What I build.

These are the recurring shapes of the systems I build. Each one gets adapted to the business it serves.

Internal Tools

Small, focused applications built for one team and one workflow.

Dashboards

Live visibility into what is actually happening in the business.

Inventory Systems

Track stock across locations, even when there is no internet.

Client Portals

One place for projects, documents and requests.

Workflow Automation

Connect existing tools and remove the manual steps between them.

Reporting Systems

The numbers the owner actually wants — not a wall of charts.

Offline Applications

Software that keeps working when the connection drops.

Data Management

Structure scattered data and give it one source of truth.

Technology is secondary. I choose the simplest stack the team can maintain and that solves the problem well — not the newest one.

About

You don't need a website. You need software that lets the business run without you chasing it.

Most of the systems I’ve built are invisible: the inventory record that is finally accurate, the report that replaced five spreadsheets, the follow-up that happens without anyone having to remember it. That is the point. Reliable systems mean fewer decisions and fewer crises for the people running the business.

I’m an engineer, not a designer. I make software that works consistently, is simple enough for a busy team to use, and stays maintainable long after launch. Boring, dependable software is a compliment.

Reliability over novelty

The system should still be running correctly three years from now — not just this quarter.

Simple enough to adopt

If the team needs training to use it, the design is wrong. It should fit the way people already work.

Outlasts the founder

It should run smoothly without someone constantly supervising it.

FAQ

Common questions, answered directly.

Short answers to the questions I hear most from business owners before they reach out.

What do you build as a freelance software engineer?

Software that removes operational bottlenecks: inventory systems, client portals, dashboards, workflow automation and internal tools for retail, logistics and service businesses.

What problems do you solve for businesses?

Scattered information, repetitive manual work, no operational visibility and follow-ups that slip through. I replace them with one source of truth instead of five disconnected tools.

How do you approach a project?

Understand the workflow first, identify the bottlenecks, design a system simple enough that the team will actually use it, build in working stages, then support and iterate after launch.

Do you build websites or software?

Software that lets the business run — internal tools, systems and automation. Not marketing websites.

What technology do you use?

The simplest stack the team can maintain and that solves the problem well. Technology is secondary; the business run better is the goal.

Contact

Let’s talk about your operational bottlenecks.

A short discovery call to understand how your business runs today, where the time goes, and whether a system can fix it. No pitch, no pressure.

Book Discovery Call Email me directly