QA Forge
Test your Windows software properly, and run the same tests again next month.
View product
// services
Web & software development
New builds, and fixing what someone else left behind.
Some projects start from nothing. Most do not. They start from something that half works. The last developer stopped in the middle. Or the tool it was built in stopped being big enough. We take both kinds. And we tell you which one you have before we quote.
// what's included
What this covers
New application builds
From the database schema up: architecture, build, testing and handover, with the code and the decisions documented as we go.
Rescue and continuation work
Inheriting someone else's codebase is normal for us. We read it first, tell you plainly what state it's in, and then work in it.
MERN, .NET, PHP, Java
The stack is chosen for the job and for who'll maintain it afterwards, not because it's the one we prefer.
Desktop software
Windows, macOS and Linux applications for work that genuinely belongs on a machine rather than in a browser.
Browser extensions
Chrome and Firefox extensions, including the review and publishing process, which is usually the part that stalls.
Rebuilds and re-platforms
Moving a working system onto something maintainable, without losing the behaviour your team relies on.
// how we work
How a project runs
01
We look at it properly
Existing code, existing data, existing constraints. No quote before we understand what's really there.
02
You get the plan in plain language
What we'd build, in what order, what's risky, and what we'd deliberately leave alone.
03
Build, review, hand over
You see working software during the build, not only at the end — and the handover includes the knowledge, not just the files.
// tools we use
Products that come out of this work
Built during real projects in this area — available to you directly.
// faq
Questions about Web & software development
Yes, and it's a large part of what we do. We'll read the codebase and give you an honest assessment first — including if the honest answer is that a rebuild is cheaper than the rescue.
By the requirements, the integrations and who has to maintain it after we hand over. If your team knows PHP, building you something in a stack nobody there can read is a disservice.
Once a project is paid for in full, the code, designs and content are yours — unless we've agreed otherwise in writing, for example around third-party licences.
It usually does at least once. Changes get quoted as changes, in writing, before they're built — no silent scope creep and no surprise invoice.
// next step
Tell us what you're dealing with
We will look at it properly. Then you get a clear explanation and a real number.