Custom software developmentProducts built
end to end.
A written scope, a fixed first increment, working software in your cloud inside six weeks. Then we keep going, or we hand it over with a runbook.
Scope in 3 days
Two pages: in, out, cost.
Six-week increments
Fixed scope, working software.
Handover pack
Runbook, tests, walkthrough.
Engagement
Built · fixed scope per increment
What you get.
A two-page SOW three days after the call: what is in, what is out, what it costs
A fixed first increment: six weeks, working software in your cloud account
A fortnightly review you sign: shipped, slipped, cost against plan
A handover pack: runbook, tests, a recorded walkthrough, a week of questions answered
Engagement: Built · fixed scope per increment · Ask about your build →
Good for
— A new product or module with a deadline
— A rebuild the in-house team cannot fit in
— An MVP that has to survive its first customers
We will say no when
— The deadline, the scope and the budget are all fixed and none of them can move
— You want a team that builds whatever the spec says and never pushes back
Stack · only what we have shipped to production
From the record.
All case notes →01 · Fintech · payments
Built · product-led
Embedded payments and stored-value wallet platform
Problem — Merchants needed to take card, wallet and BNPL payments behind one integration, and onboarding could not depend on a manual review queue.
What we did — Built from zero: self-serve onboarding with automated KYC document verification, KYC-verified adult and child wallets, subscription billing, PCI-DSS compliance, and fraud and anomaly detection across payments and reward balances. Checkout conversion was the metric; payment-method mix decided what got built next.
Measured — 0 → 150+ merchants and 100K+ transactions in four months of launch.
Client withheld · details on the callRead the case note →
02 · Digital signage · SaaS
Built
Multi-tenant digital signage platform, one engineer
Problem — A company needed its own signage product: tenants, a CMS, a player it controlled, and devices that keep working offline.
What we did — Multi-tenant backend and CMS, a custom Android (AOSP) player, offline-first device sync over MQTT, an MCP-based AI concierge, credit-based AI monetisation and a white-label reseller tier, on a lean deployment stack. Architected and built by one engineer.
Measured — Live in production with its first tenant, one of Lahore’s fastest-growing restaurant chains.
Client withheld · details on the callAsk about this →
03 · Logistics
Built
Real-time freight dispatch and load board
Problem — Dispatchers were assigning loads from stale data; delays and errors compounded through the day.
What we did — WebSockets for instant load status, driver availability and assignments. Live vehicle tracking and route planning on Google Maps. A modular React load board with revenue and broker-performance analytics over GraphQL/Apollo.
Measured — Dispatch delays and errors down — [ADD THE NUMBER].
Client withheld · details on the callRead the case note →
Custom software · the call
Tell us what you want built. We will tell you what it costs.
Bring the problem, not a brief. If it is outside what we do well, we will say which of our contacts to call instead.
Or email info@hopsig.com — reply within one working day.