Frequently asked questions
Straight answers about services, engagements and support. Anything missing? Ask us directly.
Services
What kinds of projects do you take on?
Websites and web applications, iOS and Android apps, custom software and APIs, AI features and automation, data extraction and integration, cloud infrastructure and migration, CI/CD, and debugging and maintenance. Projects that combine several of these are common.
Do you build mobile apps for both iOS and Android?
Yes. We usually recommend a cross-platform approach that covers both from one codebase, and native development when an app needs it. We also build the backend the app relies on.
Do you only build new software?
No. A large part of the work is improving existing applications: fixing bugs, improving performance, reducing technical debt and maintaining software someone else wrote.
Can you integrate AI into our existing product?
Often, yes. We look at the task you want AI to handle, the data involved and how accuracy will be checked, then recommend whether an AI model, a simpler automation or a combination fits best.
Do you take on small, single-issue jobs?
Yes. A single bug, a failing deployment or one integration is a reasonable place to start. Tell us what’s happening and we’ll suggest the smallest sensible next step.
Working together
How do projects start?
With a conversation about what you need. We then review any existing system, propose a scope and approach in writing, and begin once you have agreed to it.
How is a project priced?
Pricing depends on scope and complexity, so we don’t publish fixed rates. You’ll receive an estimate with the proposal before any work begins.
How long will my project take?
It depends on the scope. We give a timeline estimate with the proposal and update you if anything changes it.
Who owns the code?
Ownership terms are agreed in writing before the project starts. Our default approach is to commit work to your repository so it stays accessible to you.
Existing applications
Can you work on an application someone else built?
Yes. Most improvement work starts with a codebase we didn’t write. We begin by reviewing it, reproducing the issue and agreeing what to change before we change it.
What access will you need?
Only what the task requires — typically repository access and, where possible, a staging environment and logs. Access is agreed with you first.
Deployment and maintenance
Can you deploy the application for us?
Yes. We can set up hosting, environments, CI/CD pipelines and release automation, and document the process so your team can run it.
Can you move our application to the cloud?
Yes. We assess what you run today, propose an architecture with expected running costs, and migrate in planned stages with a rollback option.
Do you offer ongoing maintenance?
Yes, on terms agreed for each client — for example, a set of fixes and updates over a period, or support on request.
Can you help with a production issue right now?
Contact us with as much detail as you can. Availability for urgent work varies, and we’ll tell you straight away whether we can take it on.