Services

Ayllu builds websites, internal tools, and the systems that keep your information in one place for small businesses and organisations. I design and build them, then stay responsible for keeping them running.

You work with one person from the first conversation through launch and beyond, so nothing gets lost between planning, building, and support. Most of my clients are not technical. The systems are built so you or your team can run them.

Who it’s for

Start with the situation that sounds most like yours.

If you sell things

Shop owners who sell in person, online, or both. You need people to find you, and you want to keep your own product listings current.

If you run a service

Artists, makers, and service practices. You need a credible place for people to find you, a simple way to take inquiries, and control over your own catalogue.

If you run an operation

Small teams and mission-driven organisations. Your work runs on spreadsheets, email, and steps someone has to remember.

What I do

The work in detail, with the evidence behind each claim.

Websites and search

Websites and content platforms

For: If you sell things · If you run a service

I build websites that you can keep current yourself. Pages that repeat, such as services, products, events, or posts, follow one structure instead of being copied by hand. A change in one place stays consistent across the site.

You can use a simple editing screen in the browser, or plain files you control. I choose whichever fits the way you work. The site is built to load quickly and to work well on a phone.

Whether the content changes once a year or every week, the setup stays as simple as the job allows. There is less to maintain later.

Demonstrated by

Search and performance engineering

For: If you sell things · If you run a service

A good site is not finished when it looks right. It also has to load quickly, work on a phone, and be easy for search engines to understand.

I check how the site is built, how pages are named, and how it behaves when shared. I test the result on the real pages instead of assuming it works. Search and speed are part of the build, not something added at the end.

If something cannot be improved, I will tell you rather than promise a number.

Demonstrated by

Data and reporting

Data platforms and reconciliation

For: If you run an operation

Information often arrives from several places: spreadsheets, outside services, old records, and files someone keeps by hand. I bring it into one place and make it consistent.

Before anything is published, the system checks it and compares it with what is already there. The same person, place, or event stays on one record instead of turning into duplicates. You can see what changed, and the rules are written down so someone else can run the system without guessing.

Demonstrated by

Tools and automation

Internal applications and tooling

For: If you run a service · If you run an operation

Some jobs take weeks and depend on one person who knows the spreadsheet. I build focused tools that turn those jobs into a few clear steps anyone on your team can follow.

The tool fits the work you already do. It does not ask you to change how the business runs just to fit the software. It includes the everyday things that make a tool trustworthy: sign-in with the right access for each person, a safe test copy, and written instructions for whoever runs it.

The goal is not a big system that tries to do everything. It is the shortest path from a job that takes weeks to a job that takes a few steps.

Demonstrated by

Integrations and automation

For: If you sell things · If you run an operation

If your team copies information from one system into another, that is usually work a computer should do. I connect the tools you already use so updates happen on their own.

That might mean a record that updates itself, a status that changes when a long job finishes, or a file that arrives ready to use instead of needing to be fixed by hand.

Not every step should be automated. I start by finding the steps that are repetitive and easy to check, and leave the judgment calls with your team.

Demonstrated by

If you already have something

Modernisation and care

For: If you sell things · If you run a service · If you run an operation

Not every project starts from scratch. I take over systems someone else built, work out which parts are holding things up, and fix or replace them in stages. That avoids a risky all-at-once switch, and I document what I find as I go, so the next decision is based on evidence rather than guesswork.

I also look after what I have built: changes, improvements, updates, and the written guidance that keeps it running without me. Most people arrive with something already in place, so an assessment is often the first step.

Demonstrated by

How we can work together

Assessment
A short piece of work that tells you what you have, what is not working, and what to do next. Usually the right place to start if something already exists.
Build
A project with a clear scope, from the first problem through launch. One person handles the planning, the build, and the handover.
Ongoing support
Changes, improvements, and upkeep for something I built or took over, plus the written guidance to keep it running.

What you can expect

One person, start to finish
You work with the same person from the first conversation through launch and support. Decisions are made once, by the person who will also run what was built.
Built so you can run it
The work includes clear documentation, sensible access, and a system someone else can operate. Accessibility is checked on the real pages before anything is called finished.
Experience behind the work
Nearly twenty years of engineering across large organisations, product teams, and independent consulting. That is why a small practice can be trusted with a large organisation’s systems.

Not sure which applies? Tell me what you are working on and I will tell you where I can help.

Start a conversation