Tools you own, built around how you actually work
You know the feeling. The spreadsheet that started as a quick fix and now runs half your operations. The process that falls apart when one person is on holiday. The report that takes someone a full day to pull together every quarter. The platform you're paying for that nobody really uses.
These aren't technology problems. They're design problems. The tools you have weren't built around how your team actually works — so your team works around the tools instead.
Shipyard fixes this. We come in, figure out where the real problems are, design tools that fit how your team actually operates, and build them using modern, AI-assisted approaches. We favour open-source software and EU-based alternatives that strengthen your tech and data sovereignty — reducing dependency on big vendors and improving resilience, but we are pragmatic, building what you need, how you need it. No bloated platforms. No eye-watering licence fees. Tools you own, that do the job, and that your people can actually use.
Organisations with real problems to solve
Shipyard works best with teams who know something isn't working but aren't sure what to build — or how. If you recognise your organisation below, we should talk.
Pick how you want to work
Every organisation is different. Some want the thing built and shipped. Others want to build the muscle to do it themselves. Shipyard works either way.
Ship It
i build. you get the tools.
Think of me as your in-house technologist. I handle everything: discovery, design, development, deployment, documentation, and ongoing maintenance. You stay focused on your work. I ship fast, effectively, and to a standard that lasts.
This is the right choice when you need to move quickly, don't have spare capacity, or want someone who's done this before to just get it done.
Speed: Fast. Weeks, not months.
Your involvement: Discovery conversations and feedback loops.
You get: Deployed tools, full documentation, maintenance plan.
Learn & Ship
your team builds. i guide.
I work alongside a small team of your staff, advising and coaching them through the entire process. They do the discovery, the building, the deployment — with me there to steer, unblock, and teach. It takes a bit longer, but your team comes out the other end understanding what they built and how to maintain it.
This is the right choice when building internal capability matters as much as the tools themselves.
Speed: Steady. Longer, but your team learns deeply.
Your involvement: A small dedicated team throughout.
You get: Deployed tools, internal skills, independence.
The work draws on everything I know
Shipyard isn't just development. It's the combination of skills that means the tools we build actually fit.
AI
Modern AI-assisted approaches to design and build faster
Data
Making your data work for you, not the other way round
Design
Tools shaped around how your team actually works
Skills
Building your team's confidence and capability
Automation
Understanding what should be automated and what shouldn't
Open Source
EU and open-source alternatives for tech and data sovereignty
The kind of tools we make
Every project is different, but here are the sorts of things Shipyard produces.
Referral tracker
A housing charity replacing a shared spreadsheet with a proper system for logging, tracking, and reporting on client referrals.
Grant reporting dashboard
An automated dashboard pulling data from multiple sources so a social enterprise can report to funders without the monthly scramble.
AI-powered MCP servers
Custom Model Context Protocol servers that let AI assistants securely connect to your organisation's data — databases, CRMs, internal APIs — so your team can query and act on live information through natural conversation.
AI skills & agents
Purpose-built AI skills and agents tailored to your workflows — drafting funding applications, triaging enquiries, summarising case notes, or generating reports from raw data.
Impact data pipeline
Connecting fragmented data sources into a single, clean pipeline — with AI-assisted transformation and validation — that feeds reporting and decision-making.
Intelligent workflow automation
Automating manual processes with AI where it adds value — classifying incoming data, extracting information from documents, routing requests — and simple reliable logic where it doesn't.
Discover, assess, build, ship
Discover
Find the real problems worth solving
Assess
Work out what to build and how
Build
Design and develop the right tools
Ship
Deploy, document, and maintain
A note on technology choices
We don't build on Microsoft. Not SharePoint, not Power Platform, not Dynamics. The development cycles are too long, the licensing costs are too high, the integration headaches are too frequent, and the results rarely justify the pain.
Instead, we use open-source software and EU-based alternatives wherever possible. This isn't just a technical preference — it's about sovereignty. Your data stays under your control, hosted where you choose, governed by regulations that protect you. You're not locked into a vendor's roadmap, pricing changes, or terms of service. Open tools are faster to build with, cheaper to run, more transparent, and genuinely resilient. Your organisation will be stronger for it.
Should you build software or buy something?
The first answer is often: neither, yet. Sometimes a better process, a clearer spreadsheet, or a small change to an existing tool solves the problem. Sometimes an off-the-shelf product is good enough, and buying it is the sensible decision.
Bespoke development makes more sense when your process is genuinely distinctive, when several tools need to work together, or when control over data, portability and how the software evolves matters. But the cost is more than the first build: somebody must understand, maintain and improve it.
Discovery should leave you with a decision you can explain: what problem matters, what the alternatives are, what you could test cheaply, and whether it is worth building at all.
Questions before you commission a tool
Can we use what we already have?
That is the starting point. We look at existing systems, how information moves between them, and whether a smaller integration or a change in process would help. Replacing everything is rarely a good first assumption.
What will we own?
Shipyard is designed around organisational control and avoiding unnecessary dependency. The precise source-code, hosting, data access, handover and maintenance arrangements are agreed in the scope rather than left as assumptions.
Will our team be able to maintain it?
Documentation and a maintenance plan are part of the work. With Learn & Ship, developing your team's understanding is a core goal. With Ship It, we still agree the ownership and support arrangements before development begins.
Can we see examples?
You can explore openly published products such as Drift, which experiments with more conversational forms, and Sets, a collection of browser-based tools. These show aspects of my own building practice, not a promise that every client project will look the same.
Related support: data strategy and architecture and responsible AI and technology decisions.
Let's build something useful
If you've got problems that the right tool could solve, let's talk about how Shipyard can help.
Book a free 30-minute call. We'll talk through what's not working, explore whether Shipyard is the right fit, and outline what an engagement could look like. No pitch deck, no pressure.
book a callEngagements are scoped and quoted after discovery. We'll always agree costs before any work begins.