Custom Software Development, Owned from Architecture to Production

Off-the-shelf software fits most companies most of the time. Custom software is worth it when your process is the advantage — when bending it to a generic tool costs more than building the right one.

I take ownership of the whole path: understanding the workflow, choosing an architecture that will survive growth, building it, launching it, and staying through the first months when real usage shows what needs to change.

What I build

• Operational systems — booking, ticketing, fleet and back-office platforms.
• Customer-facing platforms — web and mobile apps with their admin and APIs.
• Integrations — connecting the systems you already have so data stops being copied by hand.

Proof

• Motamayez — an IoT ticketing system for a bus fleet: NFC cards, driver and rider apps, and a live dashboard.
• Shace — a workspace booking platform where members pick their room off the floor plan.
• Naqrat — a conversion API I rebuilt, taking response time from about 6 seconds to about 35 ms.
• iStoria — an English-learning platform I took over at 2.5M users and stabilised under load.

How an engagement runs

1. Discovery — the workflow, the users, the constraints.
2. Architecture — stack, data model and integration plan, written down.
3. Build in releases — working software early, then iterations.
4. Launch and hardening — monitoring, performance and handover.

Building a product to sell rather than a system to run? See SaaS development. Validating an idea first? See MVP development.

FAQ

Which technologies do you use?

Go, PHP/Laravel, TypeScript/React and Flutter for most projects, chosen for the problem and your team's ability to maintain it.

Do you work with our existing team?

Yes — either leading delivery alongside your engineers or owning it end to end and handing over.

What happens after launch?

A hardening period with monitoring and fixes, then either ongoing support or a documented handover.