
The problem
For owners and heads of digital who need software built.
That might be a product idea, a customer portal, or an internal tool that has outgrown its spreadsheet. Or a first version that now has to become a real product.
Quotes measured in months, with the price rising as you go.
A first version built fast that nobody can safely change.
No tests, no documentation, and one developer who knows how it works.
Nobody is sure who owns the code, the domain and the hosting.
Accessibility and security left for later, which means never.
What HAE delivers
Working software, released to real users, that your business owns and can keep improving.
- Web applications and customer portals,
built for the people who will use them every day.
- Mobile apps,
where a phone is the right tool for the job.
- Internal tools
that replace the spreadsheet everyone is afraid to touch.
- First version to production.
The smallest version worth releasing, then steady improvement based on what users actually do.
- The foundations.
Tests on every change, accessibility and security checks before release, hosting in your accounts, and documentation.
How an engagement runs
Define.
Who the users are, what they need to do, and the smallest version worth releasing. We write it down and agree it.
Design.
Flows, screens and data, reviewed with you before anything is built.
Build in reviewed steps.
Engineers build each piece. Every change is reviewed and tested. You see progress every week.
Test and release.
Accessibility, security and performance checks, then a release to real users.
Improve.
We watch how the product is used and agree the next fixed-scope piece of work.
What you get
- A written scope for the first version, agreed before work starts.
- Designs for every screen, at phone and desktop size.
- Working software, released to real users.
- Automated tests that run on every change.
- Accessibility, security and performance checks before each release.
- The source code, hosting, domain and accounts, in your name.
- Documentation and a handover session.
- A written plan for what comes next.
FAQs
Do you build mobile apps as well as web apps?
Yes. We build for the web first where that serves users well, because it is faster to release and easier to maintain. Where a phone’s camera, location or offline use matters, we build a mobile app.
We already have a first version. Can you take it on?
Yes. We start with a short review of the code, hosting and security, then agree what to fix and what to build next. If the first version is in trouble, our Harden service covers rescues.
How do you keep the product maintainable?
Tests run on every change. An engineer reviews every change before it is merged. Everything is documented as we go, and the structure stays simple enough for another team to pick up.
Who owns the code?
You do. Everything we build for you belongs to your business: the code, the designs, the documentation and the accounts. We put it in your name from the start, not at handover.
Will the product be accessible?
Yes. We build to the Web Content Accessibility Guidelines at level AA and check every release against them. Accessible products are also easier for everyone else to use.
What does it cost?
Each piece of work has a fixed scope and a fixed price, agreed before it starts. There is no hourly billing. If the scope changes, we agree the change and its price before doing it.
Describe the product. We will tell you the smallest version worth building.
Book a call, or send a few lines about what you have in mind. We reply within one working day.