Frequently Asked Questions
Practical answers about planning, costs, software development, AI, ownership, security and support.
Software development and AI: your questions answered
Start with the topic that matches your decision. Each answer links to more detail where it is useful.
Scorchsoft is usually the right fit when your project has business importance, technical complexity, or a need for careful judgement. We are not just here to write code from a brief; we help you challenge assumptions, reduce risk, and shape the right solution before money is spent building the wrong thing.
We have over sixteen years of experience solving a wide range of technical and business challenges, from working alongside existing development teams and supporting legacy systems, to building complex features and integrating systems, processes, and applications.
If you are simply looking for the cheapest build-only supplier, we may not be the best match. If you want a team that can think commercially, communicate clearly, and deliver robust software that supports your wider goals, Scorchsoft is likely worth speaking to.
A software project is usually worth exploring when the problem is expensive, frequent, strategically important, or difficult to solve with off-the-shelf tools. If the idea only creates a small convenience, or if an existing product already solves most of the problem, custom development may not be the right first step.
When we speak with you, we will help you test the commercial case, clarify the value, and decide whether the project is worth pursuing before you commit to a larger build.
That is completely fine. Many clients speak to us before they are ready to start development. We can help you understand your options, sense-check the idea, identify risks, and decide what needs to happen before a build would make sense.
If the best next step is research, process mapping, prototyping, an AI disruption assessment, or no project at all, we will tell you. The aim is not to push you into development; it is to help you make a good decision.
We are not usually the right fit for projects where the only priority is the lowest possible cost, where there is no clear business owner, or where the requirements are expected to change without active collaboration. Good software needs clear goals, honest communication, and sensible decision-making from both sides.
If your project needs a thoughtful technical partner who can challenge assumptions and help shape the right solution, we are much more likely to be a good fit.
Start by clarifying the problem you are trying to solve, who it affects, and why it matters. The idea itself is important, but the value usually comes from understanding the pain, the people involved, and what a successful outcome would look like.
If you share your idea through this form, one of our team will respond within one working day by email or phone. If you would prefer to speak to us directly, call 0121 724 0447, and one of the team will talk through your idea and project with you.
Scorchsoft is a collaborative business. We aim to build strong working relationships with our clients, and we are happy to help you understand whether your idea is worth exploring, what the next step should be, and whether we are the right fit to support it.
Yes. Scorchsoft has an in-house design team that creates visual assets, branding elements, and user experience-led interfaces for complex applications.
Yes, we can often work with third-party designs if they are production-ready. If they are not quite ready for development, we can help turn them into production-ready designs as part of our service.
If you are unsure, send us what you have created so far. We will review it, advise on the best way forward, and let you know whether we can work with the assets you have supplied.
Yes. Scorchsoft has an in-house team of developers, designers and project specialists based in Birmingham. You work with the people planning and delivering the software. About Scorchsoft explains our team and approach.
Yes, where requirements and dependencies can be defined clearly enough. Fixed-fee delivery agrees a specification and commercial scope up front; changes are assessed for their effect on cost and timing.
Velocity Sprints agree a fixed-cost increment of work, while traditional Agile uses an agreed capacity and prioritised backlog. An initial whole-project estimate is still a forecast. Our process explains the choices, or you can request a quote.
Yes. We will always try to give you a ballpark or approximate price as early as possible, usually during your first call or email exchange. A rough idea of expected cost helps you decide whether the project is commercially feasible before investing more time into detailed planning.
Ballpark estimates are educated guesses based on our experience, so the final cost may go up or down once we explore your requirements in more detail. The more information you can provide, the more accurate our estimate is likely to be.
We will also help you think about whether the likely investment makes sense against the value of the problem you are solving. If the commercial case looks weak, we would rather identify that early than encourage you into a project that should not happen.
We do this either by iterating quickly, so you can see progress and give feedback as we go, or by creating clear project documentation such as technical specifications, wireframes, and acceptance criteria.
Before we build, we also try to understand the reason behind the requirement. That matters because sometimes the requested feature is not the best way to solve the actual problem. Where appropriate, we will challenge assumptions, suggest alternatives, and help you make decisions that are easier to defend commercially and technically.
We have extensive experience delivering technically complex projects, and that experience has helped us develop a reliable delivery process. The aim is simple: clear communication, strong project control, and software that meets the agreed requirements.
We support clients in several ways, including regular meetings, project updates, status reports, and direct communication with the project team. We want you to stay informed throughout the process, so you can have confidence in both the delivery and the decisions being made.
If you have specific expectations around project management, such as how often you want updates, what documentation you need, or what support you expect after launch, let us know. We will do our best to accommodate your requirements.
Timing depends on scope, technical uncertainty, integrations, migration, testing and how quickly stakeholders can make decisions. A focused first release can take weeks; a more substantial system can take months.
Velocity Sprints normally use two-week increments, but a sprint length is not a promise that the complete application will be ready in two weeks. We agree a roadmap, dependencies and acceptance arrangements, then update forecasts as evidence improves. See our process.
We agree a delivery approach that fits your uncertainty, budget and decision-making needs. Velocity Sprints use short, scoped increments; traditional Agile prioritises an evolving backlog; fixed-fee waterfall delivery works from an agreed specification.
Your agreement defines reviews, scope or capacity, dependencies and change control. In Velocity Sprints, new priorities normally enter a later sprint; a material change requires an explicit review of its effect. Our process explains how planning, delivery, testing and continuity fit together.
Scorchsoft uses several testing approaches to improve reliability. These can include unit testing, development testing, regression testing, and internal release testing before we hand the product over to you.
At the end of a project, or at suitable points during development, we will give you the opportunity to carry out user acceptance testing. This helps confirm that the application meets your requirements. The timing and structure of user acceptance testing depends on the project management approach, whether that is waterfall, agile, or velocity sprints.
Yes, we involve you in testing. We value client feedback and want you to be actively involved in assessing the delivery, while also making sure you do not need to spend unnecessary time reporting obvious issues. Our team’s focus is on robust, reliable delivery.
Automated testing can form part of the agreed assurance approach, alongside integration, regression, release and user acceptance testing. The appropriate coverage depends on the application’s risks, architecture and delivery scope.
We agree the testing responsibilities and acceptance criteria rather than assuming that one method is sufficient for every project. For AI features, evaluation against representative examples is important alongside conventional software tests.
Payment terms depend on the engagement. Fixed-scope projects may use agreed stages or milestones; sprint delivery uses committed increments; ongoing services follow their agreed billing schedule.
The proposal and contract set out amounts, timing and the effect of changes. We explain those commitments before work begins.
Yes. We typically use React Native for cross-platform iOS and Android apps, with native development where the product requires it. The right choice depends on users, device features, integrations and the team maintaining the app.
Launching on both platforms is not always necessary for a first release. We can help you choose the smallest useful starting point. Our React Native versus Flutter guide explains the trade-offs.
Yes. Scorchsoft has extensive experience building web applications, and we can develop new web apps or support existing ones.
Clients often come to us with specific ideas about how their web app or progressive web app should function, or with particular technologies they want to use. If you have preferences for your project, share them with us when you get in touch and we will let you know whether we can accommodate them.
Potentially. An AI-built prototype can be valuable evidence of the product you want, but working screens do not establish whether its code, security, data handling and deployment are ready for real users.
An App Rescue Assessment reviews the codebase and recommends whether to support it, stabilise it, use it as a reference or rebuild. Assessment and subsequent delivery are scoped separately; we do not assume a rebuild is necessary.
We choose technologies around the product, existing systems, integrations and future ownership. Our work includes React and React Native, Node.js, Next.js, TypeScript, Python and Laravel, alongside other suitable platforms.
We can assess an existing stack or recommend one. Browse our technologies for the kinds of work each supports; framework choice alone does not determine whether a project will succeed.
Yes. We have extensive experience integrating third-party systems and existing platforms. Before we start, we need to understand what you use, what you want to achieve, and whether the systems involved can support the required level of integration.
We usually audit the systems we plan to connect with, so we can check compatibility and identify any risks before development begins. While we have a strong track record with third-party integrations, this step helps ensure the solution will work effectively for your needs.
Please contact us about your requirements, and we will advise on what we think is possible.
Payment handling can seem straightforward, but the best approach depends on what you are selling, where you are selling it, and how users will access your product.
For example, if you have a mobile app and want to accept in-app payments, the type of product or feature you are selling may determine whether you can use providers such as Stripe or PayPal, or whether you need to use Apple or Google’s in-app payment systems.
Our team can help you understand the options and recommend the best approach for your situation.
Yes. We have extensive experience working alongside internal technical, design, and marketing teams.
The best collaboration model depends on your team’s working culture, how you prefer to communicate, the technologies you use, and the kind of support you need from us. If you are unsure how we could work together, one of our team can talk through the options and help determine whether we would be a good fit.
Yes, where a custom application earns its build and ongoing ownership cost. A spreadsheet-to-app project can introduce controlled workflows, permissions and shared records. Bespoke CRM development can support distinctive sales processes and integrations.
We also consider improving the spreadsheet, connecting existing software or configuring a product such as OpsUPLOOP, rather than assuming replacement is necessary.
Start with our AI Disruption Risk Assessment to explore possible threats and opportunities. If you need a detailed review of your processes, data and priorities, AI opportunity planning can turn those questions into a practical, costed roadmap.
AI is useful when interpreting, searching, extracting or generating information creates a measurable improvement. Conventional rules, an API integration or a process change can be more suitable where the task is predictable.
We start with the outcome and compare the options. Business automation and AI opportunity planning can help establish a sensible first step.
Use an existing product when it meets the need with acceptable cost, integration and controls. Bespoke development becomes more attractive when workflows, permissions, data access or the user experience require material customisation.
The answer can also be a hybrid: keep existing tools and add a focused integration or application. Our bespoke CRM page explains that decision alongside OpsUPLOOP as a possible product starting point.
Yes, where suitable interfaces and access are available. We can connect AI features to applications, CRMs, databases and operational workflows. Permissions, validation, monitoring and human approvals should be designed around the actions involved.
See AI agents and automation development and systems integration. Our MCP versus API guide explains two related integration approaches.
Start with authorised, representative examples of the information and tasks involved: documents, records, questions or incoming requests. We need to understand quality, ownership, permissions and how success will be assessed.
A data engineering engagement can address unreliable data flows. Document processing may help when information needs extraction and validation before use. You do not necessarily need a large training dataset.
We define the business outcome, assess feasibility and data readiness, and test a bounded workflow before committing to a larger rollout. Representative evaluations, human review, permissions and failure handling help establish whether the system is useful enough to operate.
An AI Opportunity Sprint can establish the roadmap. We also plan ongoing monitoring and ownership; a promising demo is not proof of production reliability.
Often, yes. AI can help with reading, classifying, extracting, summarising and drafting, while conventional automation handles predictable rules and system updates.
We map the process and choose the simplest reliable combination. Business automation explains the approach; the Managed AI & Automation Improvement Programme suits organisations that need an ongoing cycle of identifying and delivering improvements.
Yes. AI opportunity planning maps the process, compares tools and defines data access, approvals and evaluation. The result can recommend a custom build, a product, an integration or a simpler process change. The planning scope is agreed separately from implementation.
A private AI knowledge assistant can retrieve approved information to support answers, with citations and access controls. Access should reflect each user’s permissions, including when sources change or are removed.
Private does not automatically mean on-premises hosting or no external processor. We agree providers, processing locations, retention and access requirements before live use.
We assess representative tasks and difficult cases against agreed criteria, including unsupported answers, incorrect extraction and actions taken without authority. Citations should support the answer rather than merely look plausible.
Human approval is appropriate where an error could have a material consequence. Some actions can be reversed; others need a compensating action or human intervention. Evaluation, monitoring and recovery requirements are scoped around the workflow.
Ownership and licence rights are set out in your contract before work starts. Bespoke deliverables are normally yours once paid for, subject to those terms. Pre-existing Scorchsoft tools and accelerators remain ours, with appropriate usage rights agreed for the delivered solution.
Third-party software, open-source components, cloud services and AI providers retain their own licences and terms. We identify the relevant dependencies and access arrangements rather than implying that every component becomes your property.
We agree security requirements around the application, its data and the consequences of a failure. The design can include role-based access, secure authentication, encrypted connections, appropriate protection of stored data, validation, audit logging and dependency checks.
Hosting, backups, recovery, monitoring and access responsibilities are agreed for the particular environment. Backup frequency, retention and processing locations should be documented rather than assumed to be identical across projects.
Specialist assurance, such as a penetration test, is separately scoped where needed. Tell us about your organisation’s security standards before planning so we can assess the requirements.
Almost certainly. GDPR may affect your business if you have a website, store customer data, or process personal information. If you get it wrong, the consequences can be serious, so it is worth taking the rules seriously from the start.
We appreciate this is a complex topic, so we have written an article on how to prepare for GDPR with practical tips to help you understand what to consider.
Scorchsoft’s team specialises in designing and developing software, but we are not qualified to provide legal advice, including advice on patents. For patent-related questions, you should speak to a specialist patent solicitor with software expertise.
Patenting software can be complex, costly, and time-consuming, especially if you want protection in multiple territories. It usually requires a strong case for patentability, significant financial resources, and a clear understanding of how the software is technically innovative.
That said, we may be able to support your patent solicitor by providing relevant technical documentation. If you decide to pursue a patent and your solicitor needs technical specifications, wireframes, or other information about your software project, let us know. We can estimate the work involved in preparing those materials.
If you are exploring ways to protect your idea, patents are not the only option. Many technology businesses also use trademarks, copyright protection, non-disclosure agreements, network effects, operational advantages, and ongoing innovation to strengthen their position. The Doblin ten types of innovation is a useful framework for thinking more broadly about competitive advantage.
If you speak with a patent solicitor and they identify anything they need from us, please get in touch and we will provide an estimate for the support required.
Yes. Support & Maintenance looks after the application in use through agreed maintenance, health reviews and reactive engineering capacity. Momentum provides planned development of new features and improvements. Application Hosting & Lifeline covers the agreed infrastructure responsibilities.
These services solve different needs and are agreed separately. Coverage, service hours, response targets and exclusions follow your service schedule; ongoing support is not automatically included in every build.
Yes. Just because we have built something does not mean it cannot change. For example, we can make parts of your app editable through a content management system, so your team can update content themselves. If you have additional features in mind, we can often extend the application over time as part of your product roadmap.
Some future changes depend on architectural decisions made early in the project. We may need to build certain features in a particular way to support later extensions, so it is worth discussing your longer-term goals with our technical team as early as possible.
The more you tell us about your future plans, the better we can advise you on how to structure the application for growth.
Yes. We can provide managed hosting or work in your organisation’s own cloud account where access and responsibilities can be agreed. The architecture should match availability, performance, data handling and recovery needs.
Application Hosting & Lifeline explains the infrastructure service. Application bugs and feature changes require the relevant application support or development arrangement. We can work alongside your internal IT team or MSP.
Depending on the solution, running costs can include hosting, support and maintenance, planned development, third-party licences, messaging or payment services, and AI model or API consumption.
We identify likely recurring dependencies during planning and agree what each service includes. A development quotation does not automatically cover every operating cost. Application continuity plans explains how support, hosting and ongoing development fit together.
You do not need a finished brief. Start with the problem, who it affects and what a useful outcome would look like. We can help you decide whether planning, a prototype, an assessment or a build is the right next step.
If you prefer to explore first, Execute Your Tech Idea is Andrew Ward’s practical guide for non-technical readers. You can also explore our services or contact us.
Andrew Ward has written three books that address different parts of building and running a business:
- Execute Your Tech Idea: qualifying, planning and delivering a technology project.
- The ChatGPT Guide for Business: practical AI use and prompt engineering at work.
- The Control Standard: ownership, judgement and becoming someone leaders can rely on.
For wider reading, The Lean Startup covers testing assumptions and learning from a first release; Traction explores routes to customer growth. These are resources to support your decisions, not prerequisites for talking to us.
Please let us know.
We do not offer formal in-person work experience placements. As a small, busy team, we receive more requests than we could accommodate, sometimes several every day, so unfortunately we cannot support ad-hoc placements either.
Instead, we have created a Work Experience Guide to help students build practical experience independently. This is often a faster and more effective route. If you complete a project using the guide, you are welcome to send it to us. We can provide constructive feedback in lieu of an in-person placement and write a feedback letter that you can show to your school or potential employers.
This approach enables us to support far more people than we could through in-person placements alone.
What next?
You are likely here because you have an idea, a technical challenge, or a business problem you want to solve. If you are still exploring, you may want to look at our capabilities, browse our case studies, or use our AI disruption risk report to understand where AI could threaten or improve your business.
If you are serious about moving forward, the best next step is a short conversation. We will look at what you are trying to achieve, what is driving the need, and whether it makes sense to explore further. If we are not the right fit, we will say so. If there is a simpler route than custom development, we will say that too.
Use the contact form or call us on 0121 724 0447. We will get back to you within one working day.
Need help building your ideas?
Tell us where you're headed and we'll come back with our thoughts, a realistic plan and a rough cost estimate. Scorchsoft is a UK-based team of app, portal and AI developers, working in-house from Birmingham's Jewellery Quarter.