Software development
Web applications,integrations and AI.
We design and build portals, internal applications and integrations. Where AI is useful, we agree how to check its output and control its running cost.
What you can commission
Choose what you need to build.
A complete application or a module in an existing project. These examples help define the work; the proposal sets its scope.
A customer portalRequests, documents and follow-up in one place.
- Customer request
- Team review
- Shared status
- What we build
- Customer and team views, access by role, request history and document handling.
- What we define together
- Who uses it, which steps need approval and which records come from your existing systems.
Interactive prototype with sample data. No live AI or customer connections.
An internal applicationA working tool for the people running your business.
- Assigned task
- Team workspace
- Work history
- What we build
- Screens for the agreed tasks, a shared database, permissions, search and reports.
- What we define together
- The daily workflow, the people responsible and the information the team needs to make a decision.
Connected applicationsMove records between the tools you already use.
- Source record
- Validation
- Destination system
- What we build
- The agreed connections, field mapping, validation, error reporting and recovery instructions.
- What we define together
- The system that owns each record, available APIs and how to deal with duplicates or a failed connection.
AI for documentsFind information and prepare work for review.
- Source document
- Proposed fields
- Human review
- What we build
- A document search or extraction workflow with source references, review controls and usage limits.
- What we define together
- An authorised sample, what counts as a correct answer and when a person must take over.
Interactive prototype with sample data. No live AI or customer connections.
Before writing code
Four decisions before we start.
- Users
- Who needs to use the application?
- Work
- What must they be able to do?
- Systems
- Where does the information come from?
- Acceptance
- How will we check it works?
From the first brief to handover
How we develop your project.
We agree scope, price and acceptance tests before development. You can review working versions and request changes against that agreement.
Scope example
A private request portalCustomer
Sends a request and its documents.
Private portal
Records the case, its status and history.
Your team
Reviews, requests changes and resolves.
Documents, access permissions and decisions.
Connections to your CRM or document system are defined in the scope.
What we would test
Examples to agree before development.
A request reaches the team
- When
- A customer sends the form and a document.
- Expected result
- The team sees the request and the customer can check its status.
Each customer sees their own records
- When
- A customer opens the portal or tries another request’s address.
- Expected result
- They can only access the cases and documents their role allows.
A correction keeps its history
- When
- The team asks for a change to a document.
- Expected result
- The customer sees what to correct. The previous version and the decision remain in the case history.
At handover
- Code and configurationApplication and setup instructions.
- Acceptance testsThe agreed cases and their results.
- An operating guideAccess, recovery and maintenance.
The proposal also sets out hosting, third-party licences, maintenance and who is responsible after launch.
How we deliver the projectTechnical assessment
A technical review before you decide.
You can commission a review of the systems, access and an agreed work sample. The written recommendation explains the options and dependencies before you decide on development. This assessment has its own scope and price.
Start with the free visual assessmentFor agencies and product teams
Development for agencies and product teams.
Need a module, a connection or a complete application? We agree responsibilities, repository access, code review and handover with your technical team.
Discuss a collaborationYour project
Make the decision with the right information.
Scope, investment and continuity. These are the questions we work through before a project starts.
Before commissioning software
Questions worth settling early.
How much does a custom application cost?
The price depends on the workflows, user roles, integrations and data migration. We agree a written scope and budget after reviewing those requirements. Hosting, maintenance and external services are listed separately.
Can you work on an existing application?
Yes. We first review the repository, documentation, deployment and available access. This lets us decide whether to extend the application, build a module or replace a specific part.
How do you decide whether to use AI?
We test an authorised sample against agreed tasks and review the quality, sources, data handling and cost per use. A person should review consequential outputs.
What happens after launch?
The proposal defines source code and access handover, hosting, documentation and any maintenance. We agree responsibility for incidents and future changes before launch.