{ About }
The technical team youdon't have to manage.
The Random Stuff is a UK software company. We design, build, test and support digital products for founders and established teams, with senior technical leadership included, not sold separately.
Trusted by
{ Our story }
How we got here.
We did not set out to become a fractional CTO practice. We got there because our clients kept asking for it.
Where it started
A development shop, building other people's ideas.
The Random Stuff began the way most software companies do: founders came to us with an idea, and we built it. Mobile apps, web platforms, a lot of late nights. The work was good and the products shipped. Apps like Kharis came out of that period.
What changed
The build was never the hard part.
The same pattern kept repeating. Clients did not struggle because the code was wrong; they struggled because nobody senior was helping them decide what to build, what to build it on, or what to do after launch. They were buying developers when what they actually needed was a technology function.
Where we are now
One partner for the whole journey.
So we changed what we sell. Today we take on the whole thing: strategy, design, development, testing, launch and ongoing support, with John leading the technical side personally. Clients like Baseline Mentoring, Docuports and Motiv did not hire us for a project. They hired us as their technical team.
{ Founder & CTO }
The person leading it.
John AkpenyiFounder & Chief Technology Officer
John founded The Random Stuff and still leads the technical side of every engagement personally. Architecture decisions, technology choices and the delivery plan are made by the person you meet on the first call, not handed to an account manager and passed down a chain.
That is the part most teams cannot buy anywhere else. Agencies give you capacity, advisors give you opinions; very few give you one senior person who both sets the direction and is answerable for whether it worked.
What John does on your project
- Owns the technical planArchitecture, technology choices and the delivery roadmap, decided with you, not presented to you.
- Sits in your callsNot a kickoff appearance. John stays in the working conversations for the life of the engagement.
- Reviews the work before it shipsEvery release gets senior review, so quality does not depend on which developer picked up the ticket.
- Is the person you call when it breaksOne escalation path, in UK hours, to someone who can actually make the decision.
{ The team }
A senior team, built around your product.
You get one point of technical accountability and the specialists to execute behind it, sized to what your product actually needs.
Developers
Mobile, web and backend engineers who build the product and keep it maintainable long after launch.
Design
Product and interface design, so what gets built is something people can actually use.
QA & testing
Structured testing before release, on real devices, so problems are found by us and not by your users.
DevOps & infrastructure
Deployment, monitoring and the unglamorous plumbing that decides whether a product stays up.
{ How we work }
Four things we commit to.
- 01
One accountable partner
Strategy, design, build, testing and support sit with the same team. No handoffs between agencies, no gaps for problems to fall into, and one person answerable for the result.
- 02
UK hours, real conversations
We are UK-based and work your day. A question does not cost you a twelve-hour round trip, and a fix does not wait for a time zone to wake up.
- 03
You own everything
Code, infrastructure, repositories and accounts are yours from day one, in your name. If you ever want to take the product elsewhere, nothing here is designed to stop you.
- 04
Senior review on every release
Nothing ships on the assumption that it is probably fine. John reviews the architecture and the release, so the standard does not move depending on who was available that week.
Recognised by
{ Questions }
Before you get in touch.
Who will I actually be working with?
John leads the technical side of every engagement, and you will have direct access to him throughout. Behind him is a delivery team of developers, designers and testers sized to your project. You are not passed to an account manager after the sales call.
Is John involved day-to-day, or just at kickoff?
Day-to-day. He owns the technical plan, joins the working calls and reviews releases before they ship. The depth of involvement flexes with what the project needs, but he does not disappear after the first month.
Where is the team based?
We are a UK company and work UK hours. You can raise something in the morning and have it resolved the same day rather than waiting on a time zone.
Do we own the code?
Yes, entirely. Code, infrastructure, repositories and third-party accounts are in your name from day one. Nothing about the setup is designed to lock you in.
What happens if we outgrow you?
Then we have done the job. Several partnerships have moved from us building everything, to us supporting an in-house team, to advisory only. Because you own the code and the infrastructure, that transition is a decision rather than a negotiation.
