Most projects don’t fail because they’re built badly.
They fail because they’re built for the wrong problem.
I take responsibility for the digital systems small companies depend on. The work starts with deciding what should be built, because that is the decision everything else inherits.
The obvious answer would have killed the business.
A recruitment company came to me running its operation on spreadsheets, email threads and shared folders. The obvious answer was applicant tracking software.
Applicant tracking systems are built for direct hiring, so they eventually show the employer the candidate’s name and phone number. This company’s entire business is being the permanent intermediary between the two. Any competent developer would have installed the correct product and quietly removed the reason the company exists.
That gap is where I work. Not building things faster, and not building them better than an engineer would. Working out what should be built, and holding that decision firmly enough that it survives the build.
Four ways I take responsibility for a system.
Product definition
Working out what a system needs to do before anyone starts building it. Business rules, constraints, scope, and the things that must not be built.
Building
Web platforms and internal tools, delivered through AI-assisted development. Multi-role applications, workflow systems, integrations.
Digital systems ownership
Ongoing responsibility for the things a company depends on and cannot staff for. Websites, search visibility, accessibility, technical support, the systems that quietly hold operations together.
Positioning and messaging
Working out what a company is actually selling and why the market is not hearing it. Five years of writing and content strategy sit behind everything above.
Two systems, live and in use.
Multiphase Workforce Platform
A recruitment platform rebuilt so clients can evaluate real professionals without ever being able to identify them — live, with real candidates and client organisations.
View case study →BriefStack
An AI tool that generates structured content briefs and deliberately refuses to write the content itself — live, unproven, and honest about it.
View case study →