Custom web applications and internal tools
Not every problem fits an off-the-shelf product. I build web applications around the way your team works, from the first version to production, and add AI where it saves time.
Tell me about your projectThe problem
A lot of important work runs on spreadsheets, email threads and a patchwork of tools that don't talk to each other. That works until the volume grows, someone is on holiday, or nobody can find the latest version.
Standard software often covers most of the need and forces workarounds for the rest. A focused custom application can be smaller, quicker to use and cheaper to run than you'd expect.
How I approach it
Understand the work
I start with the people who do the work: what they do every day, where it gets stuck and what the result should be.
A first version quickly
A small, working version that real people use early on, so we learn what matters before building more.
Built to last
Proven technology, automated builds and tests, monitoring and backups, so the application keeps running after launch.
Connected to your systems
Sign-in with your existing accounts, and links to the CRM, accounting software, SharePoint or databases you already use.
AI where it helps
Language models for reading, summarising and sorting, with checks around them. Not as a gimmick.
What to watch out for
- Building too much at once. A small first version that people use beats a big plan on paper.
- Forgetting who maintains it. Agree up front who runs, updates and pays for the application.
- Copying the spreadsheet. A new tool is a chance to simplify the process, not just to move it.
Projects like this
Trackbase
Trackbase shows what AI assistants tell customers about a brand.
My work at TrackbaseWorld Brain Scholar
World Brain Scholar builds AI software for academic publishers.
My work at World Brain Scholar
A private AI workspace with specialised agents
A self-hosted chat environment with agents for different tasks, so the team can use AI without sending data to a public chat app. A separate API layer logs usage and caches answers.
- Agents for different tasks in one chat environment.
- An API layer between the agents and the model providers that logs usage and caches answers.
- Everything runs on infrastructure the organisation already has.
- Questions and documents from the team
- Specialised agents
- Layer for logs and cache
- Answers inside the organisation's own environment
A job queue for shared GPU machines
When a team shares a few GPU machines, agreeing who uses which one gets messy. Now everyone submits a container job to a queue, which starts it on a machine with free resources. A web interface shows the queue, the logs and how busy each GPU is.
- Jobs are placed by the GPU memory they need, so small jobs can share a GPU and less GPU time goes to waste.
- Each job runs as the person who submitted it and can only access the folders the rules allow.
- Coding agents can submit jobs and read the results too, through an MCP server.
- Container job from a team memberFree resources on each machine
- Select a machine
- Run the job as its owner
- Logs and GPU use in the web interface
Frequently asked questions
Which technology do you use?
Proven, widely used technology, usually TypeScript or Python with a Postgres database. Where it makes sense, I adapt to what your team already uses.
Can you work with our own developers?
Yes. I can build alongside your team, take on one part of the system, or hand over a finished application with documentation.
How long does a project take?
That depends on the scope. I aim for a first version that people can use within a few weeks, and we plan the next steps from there.