What is the minimum engagement size?
The smallest paid engagement is a discovery phase starting at GBP 4,000. Build phases are quoted individually after discovery produces the evidence for a fixed price.
software development FAQ
Frequently asked questions about working with Armdia Systems
Below are the questions prospective clients most often ask before booking a discovery call. Each answer links to the page that goes deeper on the topic. If your question is not covered, the contact form sits at the bottom of the page.
Updated
Pricing questions
Questions about minimum engagement size, payment milestones, discovery cost, fixed pricing, scope management and equity.
Process questions
Questions about engagement length, client responsibilities, communication, sprint rhythm and missed deadlines.
Technical questions
Questions about preferred stack, hosting, data residency, security, code ownership and documentation.
Legal and commercial questions
Questions about contracts, intellectual property, liability, insurance and dispute resolution.
After launch questions
Questions about support tiers, emergency response, team migration and contract wind down.
How this compares to common alternatives
| Option | Best fit | Risk to check |
|---|---|---|
| Armdia Systems | Bespoke systems with clear ownership and United Kingdom first delivery. | Requires a proper discovery phase before fixed pricing. |
| Off the shelf SaaS | Standard workflows with little custom process risk. | Licence, integration and process mismatch costs can grow. |
| Freelance contractor | Small isolated tasks with limited governance needs. | Continuity, documentation and support coverage need scrutiny. |
Frequently asked questions
What are the payment milestones?
Discovery is paid upfront. Build phases are invoiced at agreed milestones, typically every two to four weeks, tied to demonstrated deliverables rather than elapsed time.
Do you offer fixed price engagements?
Yes. Discovery is always fixed price. Build phases are fixed price after discovery defines the scope, assumptions, acceptance criteria and exclusions.
How do you handle scope creep?
Changes are documented as a scope variation with a separate cost and timeline. Nothing is added to the sprint without written agreement. This protects both sides.
Do you accept equity instead of payment?
No. Armdia Systems operates on a fee for service basis. We believe clean commercial boundaries produce better engineering outcomes.
What payment methods do you accept?
Bank transfer is the default payment method. Invoices are issued in pounds sterling with payment terms agreed in the contract, typically fourteen or thirty days.
How long does a typical engagement last?
A small focused build runs six to ten weeks. A larger platform typically runs three to nine months including discovery, design, build and handover.
What do you need from the client during the project?
A named decision maker, timely feedback on demonstrations, domain knowledge, access to existing systems and time for acceptance review. Slow approvals are the most common preventable delay.
How do you communicate during a project?
A shared channel for daily questions, written architecture notes, a fortnightly demonstration of working software and a weekly fifteen minute review with the project sponsor.
What is the sprint cadence?
Two week sprints with a demonstration at the end of each. Acceptance criteria are defined before each sprint starts so progress is visible and measurable.
What happens if a milestone slips?
Slips are communicated immediately with a written note on cause, impact and revised plan. We do not wait until the end of a sprint to surface a risk.
What tooling will we need access to?
We set up GitHub, Linear and deployment infrastructure. Clients typically need a browser, email and a video call application. No specialist tooling is required.
What is your preferred technology stack?
TypeScript, Next.js with the App Router, React, PostgreSQL, Redis, Vercel and GitHub Actions. The stack is adjusted where the brief demands a different platform or language.
Where is client data hosted?
United Kingdom regions are the default. Where a provider cannot support a UK region, the exception is documented and agreed with the client before build work starts.
How do you handle data residency requirements?
We document where data sits at rest and in transit. UK or EEA residency is preferred. Provider training opt outs are enforced. Encryption uses TLS 1.3 in transit and AES 256 at rest.
What security certifications do you hold?
Companies House registration and ICO registration are active. Cyber Essentials certification is in progress. The security and compliance page lists current status.
Who owns the code at the end of the project?
The client owns all bespoke code and artefacts at handover. We retain only pre existing tools, reusable internal libraries and open source dependencies under their original licences.
What documentation is delivered?
A repository, deployment notes, architecture decision records, environment documentation and a handover session so another qualified team can operate the system independently.
What contract template do you use?
We use a master services agreement with a separate statement of work for each phase. Contracts are governed by the law of England and Wales.
How is intellectual property assigned?
Bespoke code is assigned to the client on payment. Pre existing intellectual property is licensed for use in the delivered system. The assignment clause is explicit in every contract.
What liability caps apply?
Liability is capped at the fees paid under the relevant statement of work. Professional indemnity insurance and public liability insurance are held. Specific caps are stated in the contract.
What insurance does Armdia Systems hold?
Professional indemnity insurance and public liability insurance are maintained. Certificates can be provided on request before contract signature.
How are disputes resolved?
Disputes are escalated through named contacts on both sides, then to mediation before any formal proceedings. The governing jurisdiction is England and Wales.
What does force majeure cover in your contracts?
Force majeure covers events outside reasonable control. Obligations are suspended for the duration. Either party may terminate if the event continues beyond a stated period.
What support tiers are available after launch?
Bronze covers five hours and two working day response. Silver covers fifteen hours and one working day response. Gold offers reserved capacity with same day and on call options.
How do you handle emergency incidents after launch?
Active support clients receive incident communication within four working hours of a confirmed issue. Severity, impact, mitigation and root cause are documented.
Can we migrate the product to an in house team?
Yes. Handover includes documentation, repository access, deployment notes, a walkthrough session and a transition period where questions can be answered.
How do we extend the contract after launch?
Support contracts renew on a rolling monthly or annual basis. Additional build work is scoped as a new statement of work after a short discovery conversation.
How do we wind down the contract?
Either party gives written notice as defined in the contract. Code, documentation and credentials are transferred. A final handover session is scheduled before the last day.
Can support retainer hours be used for new features?
Yes. Monthly retainer hours can be allocated to small enhancements, reporting, performance work or technical debt as long as the scope fits the reserved capacity.
Trust signals
- Concrete numbers in answers
- Links to deeper pages
Answer engine signals
- FAQPage schema
- Natural language questions
- Answers between 40 and 100 words where possible