Who actually writes it?
AI drafts, a separate review decides
A person decides what is built. Every change is independently reviewed and tested before it ships.
Anyone can ask AI for an app. Making one that is safe, that fits your business and that grows with it takes specialists. We are the AI specialists, for businesses anywhere in the world.
Turn it into a
Every business has a spreadsheet like this one. Press a button to see what replaces it.
| A | B | C | D | E |
|---|---|---|---|---|
| Mrs Okafor | 09:00 | Cut+colour | 65 | paid |
| D. Whitlow | 10:30 | Trim | 18 | ?? |
| same lady | 12:00 | colour | 65 | cash? |
| Priya (resc) | 2pm | Cut | 22 | paid |
| 15:15 | Beard | 12 | unpaid | |
| J Mensah | 16:00 | Cut+beard | 30 | paid |
Today
Tuesday, 6 jobsOutstanding
3 overdueBelow minimum
reorder before FridayBuilt by the same people with the same tools. Most are free, so try one now.
Lightmorphic VitalsFree website health and AI check.
Lightmorphic AccessFree accessibility checker.
NotespiceSelf-hosted notes as plain files.
NextupRemembers which episode you are on.
Lightmorphic DockupDocker Compose manager for home labs.
Lightmorphic PasteBrowser extension for lines you paste often.
Secure and very fast, and hosted by us.
We build both, on a base already written and tested.
Built around your business today, and changed as your business changes. A fixed quote in writing, with a completion date.
What we buildHosting, contact form and live chat included. Your site needs no cookie banner, because it sets no cookies.
What comes with oneAsking AI for an app is the easy part. Knowing what it got wrong is the job.
The repetitive part takes minutes of machine time, not weeks.
Every change goes through 42 separate checks before it ships. Every finding is fixed, even the ones that look minor, because a few minor faults put together can make a serious one.
If we misjudge how long it takes, that is our problem, not yours.
In your own words. No specification needed.
Fixed, with a completion date, in writing.
Log in early and say what is wrong.
Online software, ready to use. Your data stays yours.
Twenty-five answers in five topics, in plain words.
AI drafts, a separate review decides
A person decides what is built. Every change is independently reviewed and tested before it ships.
Yes, in full
We do not hand it over and say goodbye. We keep it running, safe and secure, with updates and fixes, as part of an annual maintenance subscription. Your data is always yours.
Written down, with a completion date
The quote is agreed before work starts. It changes only if you ask for something that was not in your description, and we tell you first.
You take your data
All exportable, and no notice period.
11,000+ in one year
New WordPress vulnerabilities were catalogued in a single year, which is why it needs constant updating. Our sites are built to be secure and very fast, without that upkeep.
Global, and it makes no difference
Registered in England and Wales, with everything done remotely. Where you are makes no difference to how quickly we answer.
No specification needed, and usually an answer back the same week.
Tell us what you needMost websites have a small file called robots.txt sitting at the top level. It has been there for decades and it tells search engines which parts of a site they may look at. Almost nobody reads it, and it does its quiet job. There is now a companion to it, called llms.txt, and it does something similar for AI assistants.
The idea is simple. An assistant arriving at your site has to work out what you are from the pages it finds. A big site with hundreds of pages can be hard to summarise, and even a small one can lead with a slideshow and a slogan. llms.txt is a plain text file, written by you, that says in a few hundred words who you are, what you do, where, and which pages matter most. It gives the assistant a map before it starts walking.
It lives at the root of the site, so its address is your domain followed by /llms.txt. It is plain text, laid out in a light style that uses a heading line, a short description, and a list of links with a sentence about each. There is no code in it and no form to fill in. You can open it in any text editor and read it as easily as a letter.
A file for a small plumbing firm might look, in outline, like this:
Write it the way you would describe the business to a new neighbour who asked what you do. Plain sentences, real facts, no slogans. The things an assistant most often needs are the things a customer most often asks, so those go first.
Keep it short. A page or two of text is plenty. If the file grows into a brochure, the useful facts get lost in it. Whatever you write must match the site itself; if the file says you open at eight and the contact page says nine, the assistant will trust neither.
This is the honest part. llms.txt is a suggestion, not a rule. It is a convention that some AI companies read and others do not, and the ones that do read it treat it as one source among many. It will not push a poor site to the top of anything. It will not make an assistant recommend you if your pages do not back it up. And it will not replace the work of writing clear pages, because the assistant reads those too.
Think of it as the label on the tin rather than the contents. A good label helps somebody find the right tin quickly. It does nothing for a tin that is empty. Your pages are the contents, and they still have to be good.
A good label helps somebody find the right tin. It does nothing for an empty one.
It is also worth saying that the file is public. Anybody can read it, including competitors. So put in what you would happily say to a stranger on the phone, and nothing you would not.
Three small files now live at the root of a well-kept site, and each does a different job. They do not overlap and none of them replaces another.
| File | Who reads it | What it says |
|---|---|---|
| robots.txt | Search engines and crawlers | Which pages you may and may not visit |
| sitemap.xml | Search engines | Here is every page and when it last changed |
| llms.txt | AI assistants | Here is who we are and which pages matter |
robots.txt is a set of permissions. The sitemap is an inventory. llms.txt is an introduction. If robots.txt blocks a page, listing it in llms.txt will not help; the two should agree. And an assistant that reads llms.txt will usually still crawl the site through the sitemap, so keep that current too.
If your site is already clear, the file almost writes itself: copy the first sentence of the home page, the key facts from the contact page, and the list of service pages with their titles. If your site is not clear, writing the file is a useful way to discover that, because you will find yourself hunting for a price or an address that is not there.
Once it is up, open the address in a browser and check it loads as plain text. Then put a note in the diary to reread it whenever prices, hours or services change, because a stale file is worse than none. We write and maintain one for every site we host, but the format is open and anybody can add one to any site. It is a small courtesy to the readers, human and otherwise, who are trying to work out what you do.