Questions people ask before they call.

We quote after a free consultation, not before. There is no price list on this site because there is no standard project. A store migration, an internal tool, and a monthly maintenance arrangement are different pieces of work with different scopes.

Here is what that means for you in practice. We ask about your business first, then write down exactly what we would build, then price that. You pay for the work you actually need, not for a package with features you will never use. You see the scope and the number before anything starts, and you approve both. If the scope changes later, we discuss and quote the change before we do it, so no invoice ever arrives as a surprise.

Yes. Small projects are normal work here, not favours.

We work with single-owner businesses, startups, growing companies, and larger enterprises. A small business often gets more out of the work than a large one, because a single well-built tool can remove a large share of the manual work in a small team. We scope to your situation. If your budget is limited, we will tell you what to build first and what can wait, rather than quoting everything at once.

Fast is the point, and it is why a lot of clients moved to us.

Support runs Monday to Saturday, 9:00 AM to 10:00 PM. Report an issue on WhatsApp during those hours and it is triaged by business impact. Anything that stops customers buying, stops your staff working, or risks data goes ahead of scheduled development work. You are told what we found and a realistic timeframe, in plain language.

We do not publish a guaranteed response time in minutes on the website, because we would rather commit to something we can honour every time. If you need a formal, contractual response guarantee, we can agree one in writing as part of a maintenance agreement. Ask about it on the call.

Both. A large part of our maintenance work is on systems built by other developers.

Typical situations: the original developer is unavailable, nothing was documented, or an internal person who managed it has left. We start by reviewing the code and the infrastructure, then give you an honest assessment of what is stable, what is risky, and what needs attention now. You get that picture before you commit to anything ongoing. Occasionally the honest answer is that a system is beyond economical repair, and we will tell you that instead of charging you to keep it alive.

That is a common starting point, and often an easier one.

If it works and needs improving, we improve it: speed, conversion, features, or stability. If it works but nobody maintains it, we take over maintenance. If you are on the wrong platform, we migrate you, keeping your data, URLs, and redirects in order so your search rankings survive the move. If it is genuinely beyond repair, we will say so and explain why, rather than selling you a rebuild you did not need.

Send us the link on WhatsApp for a quick, free read on what we would address first.

To start the conversation: your name and your phone number. Nothing else.

To write a scope and quote, we need to understand your business, the problem, and any systems the software needs to work with. That comes out of conversation, not paperwork. You do not need a written specification or technical knowledge. If you have documents, screenshots, or a list of requirements, they help, but the absence of them does not slow us down.

To start building, we need access to anything relevant, such as hosting, domains, a store admin, or existing code. We will tell you exactly what we need and why.

Yes. One call, no cost, no obligation, no contract at the end of it.

We do it because it is the only sensible way to quote work accurately, and because it is a fair way for both sides to find out if this is a good fit. If you decide not to proceed, that is the end of it. We will not put you on a mailing list or call you repeatedly. If the advice on the call is all you needed, you are welcome to take it and go.

Yes. We are happy to sign a non-disclosure agreement before you share anything sensitive, and we can do that before the consultation if you would prefer.

We treat client information as confidential whether or not an NDA is in place. We do not discuss client projects with other clients, and we do not publish work in a portfolio or case study without written permission. If your organisation has its own NDA or vendor agreement, send it over and we will review it.

We choose the stack based on what fits the project, your budget, and how the system will be maintained over the next few years. Not based on what is fashionable.

If you already have a stack, or your internal team has standards, we work within them. If you are starting fresh, we will explain the options in plain language, including the trade-offs, so the decision is yours and you understand it.

Three routes, all reaching a person who knows your project. WhatsApp is fastest and what most clients use: describe the problem and send a screenshot if you have one. Phone works for anything easier to explain out loud. Email suits non-urgent issues or when you want a written record.

Support hours are Monday to Saturday, 9:00 AM to 10:00 PM. Messages sent outside those hours are picked up at the start of the next working period. Urgent problems are prioritized ahead of scheduled work.