One system, many companies
Software that serves several client organisations at once, with each one's data properly walled off from the rest. This has to be designed in from the start — bolting it on afterwards means building it twice.
Services
Build it, ship it, keep it running.
Three disciplines under one roof. You can engage us for any one of them, but they work best together — most failures happen at the seams between separate vendors.
Software
Apps built around how you already work.
Most businesses end up bending their process to fit whatever tool they bought. We do it the other way round — watch how the job actually gets done, then build that.
- Tools your team uses every day
- Replacing the spreadsheet everything depends on
- Connecting systems that do not talk to each other
- Moving off software you have outgrown
Web
Sites that load fast and sell something.
A website earns its keep or it is a brochure nobody opens. Ours are quick on a weak connection, findable on Google, and editable by your own team without calling us.
- Company sites and landing pages
- Online shops and customer logins
- Speed, accessibility and search
- Content your team can change themselves
Systems
The plumbing, set up so it stays quiet.
Hosting, backups, email, deployments, monitoring. The part nobody thinks about until it breaks — which is exactly why we set it up so it does not.
- Hosting that survives a busy day
- Backups that have actually been restored
- Alerts that reach us before they reach you
- Email, domains and accounts in your name
Specialisms
Where we are properly deep.
Any studio will list every technology. These are the six areas where we have shipped the thing already and know where the difficult parts are.
The reports you get judged on
Attendance, exceptions, penalties, vendor bills. Delivered in the exact shape your finance and payroll teams already use, so nobody retypes anything into a spreadsheet at month end.
Selling and taking orders online
Menus, carts, coupons, order tracking, invoices — plus a live screen for the people actually filling those orders. Totals are worked out on our server, so they cannot be edited in the browser.
Security that is not an afterthought
Locked at the database, so a mistake in the website still cannot expose one customer's records to another. Passwords hashed, logins rate-limited, errors that never leak internals.
WhatsApp and delivery partners
Order updates and OTPs over WhatsApp instead of SMS, and orders from your own site pushed to delivery fleets. Our side is written and deployed; we are waiting on partner approval, not on engineering.
Dashboards people actually open
Built around the two or three decisions you make each week, not every chart the software can draw. Readable if you are colour-blind, honest about scale, and exportable from every view.
Custom software
Software shaped to your business, not the other way round.
Off-the-shelf tools make you change how you work to suit them. Custom software does the opposite — but only if whoever builds it understands the work first. We spend the early part of an engagement watching how the job is actually done, including the spreadsheet workarounds people are slightly embarrassed about, because those are usually where the real requirements are hiding.
- 01
Understand the work
We sit with the people who do the job and map what actually happens — not what the process document says. Every workaround is a requirement in disguise.
- 02
Agree the shape
Screens, data model and integration points, written down and walked through with you before any code exists. Changing a diagram is free; changing a build is not.
- 03
Build in the open
Short cycles with something running at the end of each. You get a real URL to click, not a status report, and you can redirect us while redirecting is still cheap.
- 04
Migrate and cut over
Your existing data comes across, verified against the source. We plan the switch for the quietest hour you have and keep the old system reachable until you are certain.
- 05
Train and hand over
Documentation written for your team, sessions with the people who will use it daily, and admin access in your names — not ours.
- 06
Stay on
Monitoring, backups, security patching and the steady stream of small changes that every live system generates. This is where most vendors leave.
Chatbots
Chatbots that know your business.
We build, train and run custom chatbots that sit on your website and answer as your business would — from your catalogue, your policies and your hours, not from a generic script. The same bot can serve your social channels, so a question asked on Instagram gets the same answer as one asked on your site, and both land in one inbox.
- Trained on your own content — products, pricing rules, policies, opening hours
- Embedded in your existing site with a single script tag, no rebuild required
- The same brain across WhatsApp, Instagram and Facebook Messenger
- Hands off to a human cleanly, with the conversation history attached
- Captures leads and enquiries straight into your CRM or our lead console
- We keep it trained as your business changes — it is a service, not a one-off install
Domains, mail and social
The scaffolding around the software.
A new business needs more than an application. It needs a domain nobody else can take, mail on that domain that does not land in spam, social accounts that match, and hosting that will not fall over the week you get noticed. We set all of it up together, in your name, and then look after it.
Domains and DNS
Registration, renewals and DNS — including the SPF, DKIM and DMARC records that decide whether your mail gets delivered or filed as junk.
Professional email
Mail on your own domain with role addresses that route to the right person, so enquiries do not sit in one overloaded inbox.
Social accounts
Handles secured across the platforms that matter to you, linked to the site, and consistent with the brand rather than assembled ad hoc.
Hosting and delivery
Global edge hosting with automatic HTTPS, preview deployments for every change, and rollback that takes seconds rather than an evening.
The details
The answers, before you have to ask.
The six things that usually take three calls to establish.
Who owns it?
You do. The code, the hosting accounts, the domain — all in your name from day one, not signed over at the end. If you ever want to take it elsewhere, nothing has to be untangled first.
Support ends on a month's notice. No exit fee.
Is my data safe?
Locked at the database itself, not just behind the app's login screen. So even if something in the website were broken, one client still could not reach another's records.
Postgres row-level security; writes only through reviewed procedures.
Will it be fast in India?
Yes. The pages are served from inside the country and so is the database, so nothing has to cross an ocean before it reaches you.
Vercel edge; Supabase in the Mumbai region.
What if something breaks?
We usually know before you do — the system pages us, not the other way round. Ordinary requests get answered Monday to Saturday, 9am to 7pm.
Round-the-clock outage response on a support agreement.
What will it cost to run?
Very little at first. We size the hosting to the traffic you actually have, so a small site costs close to nothing until it is busy enough to be worth paying for.
Third-party costs billed at cost, in your own accounts.
Can my team change things?
Yes. Content, prices, photos and offers are yours to edit without booking a developer. We only get involved when the thing itself needs to change.
Training and written handover included, not charged extra.
What it costs
Priced to the project, not to a bracket.
We do not publish a rate card, because we have never met two briefs that deserved the same one. What we do commit to is a written scope and a firm price before anyone opens an editor — and that price does not move unless you change the scope. Affordability is not a discount we offer selectively; it is how we scope. If a cheaper approach gets you the same outcome, that is the one we will quote.
A firm number, in writing
Not a range that widens once work starts. The quote and the scope are the same document, and changes to one are visible in the other.
Milestones, not a lump sum up front
You pay against work you can see running. Nobody carries the whole risk.
Third-party costs at cost
Hosting, domains, API access and licences are billed at what they cost and kept in your own accounts wherever possible, so you keep control of them.
No lock-in
Source, infrastructure and accounts are in your name from the first day, not transferred at the end. Support cancels on a month's notice.
Not sure which you need?
Describe the problem rather than the solution. Working out which layer it belongs to is part of our job, not yours.
Talk it through