Frequently asked questions

It begins with a conversation. Send us a short description of what you need through the project form, and we will follow up with questions about your organization, the problem you want to solve and the people who will use the system.

From there we agree the scope together, prepare a written proposal and only start building once you are comfortable with it.

It depends on the project. We do not publish fixed prices because the cost is shaped by scope, features, number of users, design, complexity, integrations, database and infrastructure needs, security requirements and the support you want afterwards.

After we understand your requirements, we give you a tailored quotation. The pricing page explains the factors in more detail.

There is no single answer. A small website and a multi-branch management system are very different undertakings. Once the requirements are clear, we can give you an estimate for your specific project.

We build in stages, so you see working software along the way rather than waiting for a single launch date.

Yes. Custom software is the core of what we do. We design systems around how your organization works, covering web applications, mobile apps, business systems, internal tools, APIs and dashboards.

Yes, we can integrate payments into websites and applications. What is possible depends on the payment provider you choose: the methods they support, their fees and their approval process.

We check feasibility against the provider's documentation before agreeing scope, and we cannot guarantee a provider's approval or pricing.

Yes. We can build mobile applications for Android and iOS, including features such as accounts, payments, notifications, bookings and orders. We can help you decide whether to launch on one platform first or on both.

Yes. We can build school management systems covering student registration and profiles, attendance, fees, results, report cards, timetables, parent and student portals, staff management and communication. We design the modules around your school's own structure and terms.

Yes, we can build administrative and operational systems for clinics and hospitals, such as patient registration, appointments, records, pharmacy and laboratory workflows, billing and reporting.

Our software does not provide medical advice. Healthcare organizations remain responsible for clinical decisions and for meeting legal, ethical, data protection and regulatory requirements.

Often, yes. We would first review the system to understand how it is built and hosted, how well it is documented and what condition it is in. Then we can recommend and agree a support arrangement.

In some cases we may recommend improving or rebuilding parts of it. We will explain why before any work begins.

We set up hosting and deployment for the systems we build, and we help plan infrastructure such as databases, backups and monitoring. Hosting and cloud services are usually provided by third-party companies and billed by them. We help you choose and plan for those costs.

Launch is the start of a system's working life, not the end of the project. We help your team begin using the system, then we can maintain it, fix issues, keep it updated and build improvements as your needs change.

The support arrangement, including what is covered, is agreed with you in writing.