---
title: "Software"
updated: "2026-11-16"
url: "https://www.etheon.com/services/software"
---

# Custom software development

Custom software development, from discovery to QA. We design, build and test software and products your team can own.

## Custom software development, from discovery to QA. We design, build and test software and products your team can own.

**01 Discovery and design** · Layer 1 of 5 · Interface

Discovery and design.

- Research and scoping
- Feasibility and prototypes
- Product design: research, UX and UI

**02 Product engineering** · Layer 2 of 5 · Product

Product engineering.

- An MVP scoped to a first release
- Accounts, roles and billing
- Staged releases

**03 Custom software and APIs** · Layer 3 of 5 · Services and APIs

Custom software. The tools, platforms and APIs your business runs on, built to your process.

- Back ends and APIs
- Internal tools and dashboards
- Documentation and a handover your team can own

In this layer: REST and GraphQL, Background jobs, Webhooks

**04 Modernization** · Layer 4 of 5 · Legacy core

Legacy modernization.

- In stages
- Tests before the code moves
- A rollback at each step

**05 QA** · Layer 5 of 5 · Delivery

Quality assurance.

- Tests in the pipeline
- WCAG 2.2 AA testing
- Performance budgets

### Discovery and design. Research, scope and a prototype before the product code.

#### What it is

Discovery and design turn an idea into a product you can build with confidence. We research your users and your market, test whether the idea is feasible, and design the product as a prototype your team can click through before any product code is written.

#### What we do

- Research and scoping
- Feasibility and prototypes
- Product design: research, UX and UI

#### How we do it

1. Research: Interviews with your users and a look at what already exists.
2. Prototype: A design you can click through, tested before it is built.

#### Questions

**What do we have at the end of discovery?**

A scoped product plan and a prototype tested with your users, so you can decide what to build before the product code starts.

**Can you work with our designers?**

Yes. We work with your design team in your tools, or lead the design where you have none.

#### What you get

- A scoped product plan
- A tested prototype

#### Stack and tools

- User research tools
- Prototyping tools
- Design tools

#### Related

- [Design systems, on Web](https://www.etheon.com/services/web?detail=design-systems#design-systems)

### Product engineering. A first release scoped, built and shipped in stages.

#### What it is

Product engineering builds a software product from its first release to a platform that grows. We scope the smallest release worth launching, build the accounts, roles and billing it needs, and ship it in stages so you learn from real users early.

#### What we do

- An MVP scoped to a first release
- Accounts, roles and billing
- Staged releases

#### How we do it

1. Scope: The first release cut to what your users need first.
2. Build and ship: Built in short cycles and released in stages.

#### What you get

- A working first release
- The code and its documentation in your repository

#### Stack and tools

- Web frameworks
- Mobile frameworks
- Authentication
- Billing platforms

#### Related

- [Jeriko, a team of personal AI agents](https://www.etheon.com/work/jeriko)
- [SaaS, on Web](https://www.etheon.com/services/web?detail=saas#saas)

### Custom software and APIs. The tools, platforms and APIs your business runs on.

#### What it is

Custom software is the tools, platforms and APIs built around how your business works. We build back ends and APIs, internal tools and dashboards, and the integrations that connect them, documented so your own team can run and change them.

#### What we do

- Back ends and APIs
- Internal tools and dashboards
- Integrations
- Documentation and a handover your team can own

#### How we do it

1. Map the process: How the work runs today, and where software helps.
2. Build and hand over: Built, tested and documented for your team to run.

#### What you get

- The software and its source code
- Documentation and a handover

#### Stack and tools

- Programming languages
- API frameworks
- Databases
- Background job queues

#### Related

- [Integration, on AI](https://www.etheon.com/services/ai?detail=integration#integration)

### Legacy modernization. The old system replaced in stages while the business keeps running.

#### What it is

Legacy modernization replaces an old system while the business keeps running on it. We map the system, wrap it in tests, replace it one module at a time with a rollback at each step, and switch the old system off when nothing calls it any more.

#### What we do

- In stages
- Tests before the code moves
- A rollback at each step

#### How we do it

1. Audit.: The system mapped, its risks and its callers listed.
2. Wrap in tests.: Tests written around it before any code moves.
3. Replace in slices.: One module at a time, each with a rollback.
4. Retire.: The old system switched off when nothing calls it.

#### What you get

- A map of the old system and its risks
- The new system, module by module

#### Stack and tools

- Test frameworks
- Feature flags
- Data migration tools
- Delivery pipelines

#### Related

- [Modernization, on Mobile](https://www.etheon.com/services/mobile?detail=modernization#modernization)
- [Migration, on Cloud](https://www.etheon.com/services/cloud?detail=migration#migration)

### QA. Tests in the pipeline, accessibility and speed checked before release.

#### What it is

Quality assurance makes sure software works before it reaches your users. We put automated tests in the delivery pipeline, test accessibility against WCAG 2.2 AA and hold each release to performance budgets agreed with you.

#### What we do

- Tests in the pipeline
- WCAG 2.2 AA testing
- Performance budgets

#### How we do it

1. Automate: Tests that run in the pipeline on every change.
2. Check before release: Accessibility and speed checked before each release.

#### Questions

**How do you test what you build?**

With automated tests that run in the pipeline on every change, accessibility checks against WCAG 2.2 AA, and performance budgets each release has to meet. A release that fails a check waits until it passes.

#### What you get

- A test suite in your pipeline
- An accessibility and performance report

#### Stack and tools

- Test frameworks
- Accessibility checkers
- Performance monitoring
- Delivery pipelines

#### Related

- [Evaluation, on AI](https://www.etheon.com/services/ai?detail=evaluation#evaluation)
- [Performance and accessibility, on Web](https://www.etheon.com/services/web?detail=performance-and-accessibility#performance-and-accessibility)
- [How we work](https://www.etheon.com/company/how-we-work)

## Legacy modernization, in steps. The business keeps running while the old system shrinks.

1. **Audit.** The system mapped, its risks and its callers listed.
2. **Wrap in tests.** Tests written around it before any code moves.
3. **Replace in slices.** One module at a time, each with a rollback.
4. **Retire.** The old system switched off when nothing calls it.

## A week in your repo. Our engineers work in your code, your tools and your rituals.

1. **Monday**: Planning, The week's priorities, with your lead
2. **Tuesday**: Pull requests, Each one reviewed before it merges
3. **Wednesday**: Design check, Open questions settled with your team
4. **Thursday**: Demo, Working software, not slides
5. **Friday**: Release to staging, With notes your team can read

**Every day**: Your repository, Your issue tracker, Your stand-up, Your pull request checks

### Working in your repo. Our engineers join your code, your tools and your rituals.

#### What it is

Working in your repository means our engineers join your team where the work already happens: your code, your tools, your planning and your reviews. Nothing moves to a system of ours, and your team sees every change as it is made.

#### What we do

- Access to your repository and your tools
- Reviews before every merge
- Your rituals: planning, stand-ups and demos

#### How we do it

1. Join: Access to your repository, tracker and channels before work starts.
2. Work your way: Your branches, your reviews and your rituals.

#### Questions

**Can you work inside our team and our code base?**

Yes. Our engineers work in your repository, your tracker and your rituals, and follow your team's reviews and conventions.

**Who owns the code?**

You do. The code, the models and the accounts are in your name, and the repository is yours from the first commit.

#### What you get

- Pull requests in your repository, reviewed by your team
- Release notes your team can read

#### Related

- [How we work](https://www.etheon.com/company/how-we-work)

## Selected work. Software we have built and launched.

- [Jeriko, a team of personal AI agents](https://www.etheon.com/work/jeriko): Etheon built Jeriko for a client: a team of personal AI agents, each a person in the app with its own memory, instructions, wallet and email address.

- [Web](https://www.etheon.com/services/web): Web apps, SaaS and e-commerce
- [Mobile](https://www.etheon.com/services/mobile): iOS, Android and cross-platform