We build and evolve the software your business depends on.

Start by describing the problem, your current tools and the change you want to make. We’ll discuss what is already clear and what needs investigating. If analysis or a specification is needed, we’ll agree its scope before work begins. You can also bring existing requirements for an estimate.

An existing tool makes sense when it supports the processes you need and connects to your other systems. Custom software is worth considering when available products need too many workarounds or limit your business. We compare not only setup costs, but also licences, integrations, data migration, maintenance and future changes.

We start with scope, integrations and the state of the existing system. If analysis or an audit is needed, we agree its scope and cost separately. Clearly defined stages can have a fixed price, while evolving work can be billed on a time and materials basis. For ongoing work, we can agree a monthly development and maintenance budget. Each model defines scope, acceptance criteria and how changes are priced.

Yes. We agree the scope of the code, integration, environment and access review. We identify who knows the system and how to fill gaps in documentation. We then plan knowledge transfer, maintenance responsibilities and the first changes.

Yes. We start by understanding the users and what already works. Once we agree on scope, we review code, data, permissions, integrations and deployment. You receive a recommendation on which parts to keep, what needs changing and where to start preparing the application for everyday use.

Before starting, we agree who sets business priorities, makes technical decisions and accepts each stage. If you have an IT team, we agree how to divide the work. We need your knowledge of the processes and users’ feedback to check the solution.

Yes. We use AI tools, including Codex from OpenAI, to support code analysis, feature development and test preparation. We adapt how we use these tools to the project and the agreed rules for handling data. Our team is responsible for technical decisions, verifying how the software works and preparing deployment.

We start with a specific task and the data the solution will use. We assess output quality, costs, response time and error handling. We compare the results with the current workflow and simpler automation. The test results guide the decision to implement AI and show where human oversight is needed.

New features, updates, monitoring and support requests. We agree the scope, availability hours and response times before starting. If an SLA is needed, we agree its terms and cost. We can also hand over code, documentation and knowledge to another team.