Calango LabE-commerce
A store that doesn’t stop at the storefront: payments, shipping and stock wired into what the company already uses. Whoever builds the store handles the integration — not two vendors arguing over whose fault it is.
Software studio · since 2013
Websites, stores and the systems that hold them up.
For companies that need more than a storefront: a store wired into stock, a portal with a members-only area, systems that finally talk to each other, and routine work that runs on its own. Twelve years building, integrating and maintaining — with development, DevOps and infrastructure under one roof, from quote to maintenance.
release — calango lab
$ git checkout -b work-orders
Switched to a new branch 'work-orders'
$ cat requirements.md
# 12 rules gathered from the people who use it
# 9 screens mapped, 3 integrations
$ npm run dev
▲ ready in 1.4s
app/orders/page.tsx ✓
lib/rules/stock.ts ✓
lib/rules/deadline.ts ✓
$ npm test
PASS lib/rules/stock.test.ts
PASS lib/rules/deadline.test.ts
2 suites · 34 tests · 1.9s
$ git commit -m "release 3: work orders"
14 files changed
$ vercel --prod
● build 42s
● system live
0Years in business
[N]Projects delivered
[N]Systems in operation
0Point of contact, start to finish
The diagnosis
Where most companies get stuck
01
The site has been live for years and has never brought in a lead that became a client.
02
Publishing a new page means opening a ticket with whoever built the site.
03
The store sells, but someone checks stock and issues invoices by hand, order by order.
04
What the company does best appears nowhere on the internet.
A good-looking site that doesn’t sell is an expense. A store that doesn’t integrate is double the work. What solves it is what sits underneath.
Services
Eight fronts, one way of working
Scope, timeline and price settled before the first line of code. What’s left out is written down, not sprung on you halfway through.
Websites and portals
No templates, with a CMS your team runs on its own — and a login area when you need one.
Maintenance and evolution
A monthly contract with support, improvements and monitoring.
Custom software
For when the process won’t fit off-the-shelf software. Research, build, and the infrastructure that holds the system up afterwards — all from the same team.
Legacy rescue
A site or system running with no documentation and nobody maintaining it. We audit it, document it, and tell you whether to fix, migrate or rebuild.
System integration
ERP, store, CRM, gateway and invoicing talking to each other — with logging, retries and alerts. Nobody exporting a spreadsheet and retyping it in the middle.
AI and automation
The repetitive work leaves the desk: triage, document extraction, reporting and support. With AI where it earns its place, without it where plain code does better — and human review where the decision carries weight.
How a system comes about
The route, in five stages
Drag to rotate, hover over the nodes, click one, or use the arrow keys. It’s the same flow every project runs through — except here you can walk it.
DiscoveryModellingInterfaceBuildRelease
01 / Stage
Discovery
Learning the rule from the people who run the process today, not from those imagining how it ought to work.
Process
How the work goes
Five stages, each with a date and a deliverable. You see the whole road before you sign — and validate each stretch before the next one starts.
Conversation
Understanding the problem. No commitment and no charge.
Assessment
A proposal with scope, timeline and price settled. You know what you are getting and what it costs before you sign.
Build
Partial releases. You validate at each step, and anything off target is corrected before we carry on.
Handover
System live, team trained, documentation in hand.
Continuity
Maintenance and evolution, so the system ages well.
The right tool is the one that’s still maintainable after handover
Technologies: WordPress, Nuxt, Next.js, PHP, JavaScript, Astro, MySQL, Tailwind.
About
Who builds it and who keeps it running
Twelve years building for the web — long enough to have watched a site launch, deliver, age badly and need rescuing. That’s what teaches you to build with what comes after handover in mind, not just launch day.
There are three of us, one per craft: development, DevOps and infrastructure. Whoever writes the system sits in the same room as whoever keeps the server standing — and it’s right there, in the seam between building and sustaining, that projects usually die.
First conversation is free
Tell us what you need. We will say if we can.
The first conversation costs nothing and commits you to nothing. If Calango Lab isn’t the best option for your case, you hear that in the first conversation — not after signing.