Software engineering
The team that builds our platform, building yours
Forenax’s engineering team builds and runs our own automation platform for accountancy practices. The same team looks after a small number of existing software clients, and takes on new engineering work only where it fits around that.
What we build
Software that has to work on a Monday morning
We build the way we build Forenax: tested, logged, documented and handed over in a state someone else can maintain.
Custom web applications
Internal tools, customer portals and SaaS products, from first version to running in production.
Integrations and APIs
Connecting accounting, CRM, forms and messaging systems so data moves without retyping.
AI features, built carefully
Drafting, reading and sorting features with human approval, logging and data kept where it should be.
Rescue and modernisation
Taking over an existing codebase, making it safe to change, and moving it to a current stack.
Dedicated developers
Engineers who join your team, managed from the UK
When you need more capacity than a project, a dedicated developer works on your product full time, in your tools and your stand-ups, a month at a time.
- Your repositories, your process. They work in your GitHub or GitLab, your tickets and your review rules.
- Overlap with UK hours. Agreed at the start, so questions get answered the same day.
- A UK point of contact. One named person in Manchester manages the engagement and is who you call if anything isn’t right.
- Month to month. Scale up or down with a month’s notice, with handover notes when someone rolls off.
- Security basics from day one. Least-privilege access, no production data on laptops, and access removed the day an engagement ends.
How a project runs
Short cycles, working software, no surprises
Scope
A call, then a written scope with what’s in, what’s out and what it costs.
Build
Work in small pieces you can see, with a demo every week or two.
Launch
Deployed with monitoring, backups and a runbook, not just the code.
Look after
Support and changes afterwards, or a clean handover to your own team.
What we work with
TypeScript · Node.js · React · Next.js · Astro · PostgreSQL · Python · REST and GraphQL APIs · AWS · Cloudflare · Docker · GitHub Actions
Questions
Working with our engineers
Who will actually work on our project?
Engineers from the team that builds Forenax’s own platform, managed from Manchester. You’ll know who is working on your code, and you can talk to them directly.
Which hours do you work?
We agree overlap hours with UK time at the start, so there is always a window for calls and quick questions during your working day.
Who owns the code?
We agree it in writing before work starts. Code you pay us to write for you is yours, and it lives in your repositories from day one.
How do you handle our data?
Developers work on test data, not your production data, unless you specifically decide otherwise. Access is limited to what the work needs, and we sign a data processing agreement where personal data is involved.
What’s the minimum engagement?
For a project, a scoped first phase. For a dedicated developer, a month at a time. We’ll tell you on the first call if the fit isn’t right.
Tell us what you need built
A few lines about the project or the role is enough. We’ll reply within one working day.
- You suggest a time
- Thirty minutes on a recent week
- A one-page map within 48 hours