/ For systems that need fixing
Rescue & Support
Your developer left, the system keeps breaking, and nobody knows how it works.
We review what you have, fix what matters first, and keep it running.
- A code and hosting review before any promise
- Urgent fixes first, a written plan for the rest
- Monthly support so it stays fixed
- Talk to the founder
- No prep needed
- No obligation
/ How it works
What you get, and when.
Teams whose software or website is broken, slow, or abandoned
Review first, then fixed or monthly
fixed price for fixes, monthly for support
Your first two weeks
Day 1
Free call about what keeps breaking
Within 3 business days
Access set up, code and hosting reviewed
Week 1
Written findings: stabilise, extend, or rebuild, with a price
Week 2
First urgent fixes live
Included
- Code and hosting review
- Security and backup check
- Bug fixes
- Documentation of how it works
- Monitoring setup
Available add-ons
- New features
- Speed improvements
- Moving to new hosting
- Rebuilding the parts that can't be saved
Quoted separately, on top of the agreed scope.
If you ever leave: We document everything we touch, so you are never stuck with one developer again.
No prep needed. Just tell us what keeps breaking.
/ FAQ
Your questions, answered.
01Can you take over or improve an existing system?Have a system to fix
Yes. We start with a code and infrastructure review, then recommend whether to stabilise, extend, or rebuild specific parts.
02Do we have to rebuild everything?Have a system to fix
Usually not. We fix what matters first and keep what works. We only suggest rebuilding the parts that cost more to keep than to replace.
03What happens on the free call?Everyone
You tell us what is slowing you down, and we ask a few questions about how things work today. You leave knowing whether we are a fit and what the first step would be. No slides, no pitch.
04How is a project priced?Everyone
After the free call, we send a fixed-price proposal with the scope, deliverables, and timeline. You know the cost before any build work begins.
05How long does a typical project take?Everyone
Focused builds such as websites or single modules usually take 2–6 weeks. Full business systems take 6–16 weeks. The proposal gives a timeline for your specific scope.
06I'm not technical. Is that a problem?Everyone
Not at all. Most people we work with are not. We talk about your business, not the technology, and explain every choice in plain language.
07Who owns the code when the project is finished?Everyone
You do. Source code, documentation, and access to your accounts and infrastructure are handed over at the end of the project.
08Who has access to our data and accounts?Everyone
Your systems run in accounts you own. We only get access to what the work needs, and you can remove it at any time.
09Is there a minimum term, and how do we stop?Everyone
Builds are fixed-price projects with no ongoing commitment. Monthly support runs month to month, and you can stop with 30 days' notice.
10What if we stop working together?Everyone
You keep everything: source code, documentation, and access to your accounts and servers. We hand over in writing so another team can pick it up.
11Can you sign an NDA before we share details?Everyone
Yes. We are happy to sign a non-disclosure agreement before you share business plans, data, or technical details.
12Do you work with clients outside Sri Lanka?Everyone
Yes. We work remotely with written updates, scheduled calls, and live demos, and agree on overlapping hours that suit your time zone.
/ Next step
Bring us the problem slowing you down. In one short call you'll know what we'd do first.
- Talk to the founder
- No prep needed
- No obligation