About
A small firm,
deliberately.
Three capabilities, one standard, and the engineer who scoped it on the other end of the email.
Keklik Technologies builds the layer businesses run on rather than the layer they show customers: the extraction that feeds a decision, the process that runs without being watched, and the system the team opens every morning. It is unglamorous work with a low tolerance for hand-waving, which is roughly our temperament.
The name
Keklik.
Keklik is the chukar partridge — a ground bird that would rather walk than fly, holds its territory on rocky slopes nothing else wants, and is recognised at a distance by the sharp black barring along its flank.
It is a reasonable emblem for this kind of engineering. The work is done on the ground, in the difficult terrain of a real operation, and the thing you should recognise us by is the pattern: the same measured method applied whether the job is a crawler, an agent, or a clinic’s appointment book.
The barring is the only ornament on this site. Everything else is a rule, a label, or a number.
Recognised at distance by the pattern, not the plumage.
Why these three
They are the same problem at different depths.
Firms usually pick one and outsource the rest, which is where the seams appear. We kept all three because the handover between them is exactly where projects tend to fail.
Data extraction
Managed web scraping — property, marketplaces, directories, reviews, search, news, and social — delivered as clean records on your schedule.
Automation
Agentic AI and workflow automation, built to survive production: bounded, evaluated, observable, and reversible.
Systems
Custom operational software — school, clinic, venue, and production management — built around how the work is really done.
A price-monitoring feed is worth very little until something acts on it; an agent that acts is dangerous until its actions are recorded somewhere accountable; and a system of record is only as good as the data arriving in it. Owning all three means nobody gets to point at the other supplier.
Structure
The constraints we chose.
Each of these costs us something. They are on this page because they are also the reasons to hire us, and you should be able to check whether we are keeping to them.
- The engineer who scopes your project is the engineer who builds it. This caps how many clients we can take at once, and we would rather turn work down than break it.
- No account management layer. It means fewer status decks and more direct answers, including the unwelcome ones.
- Every engagement is written down before it starts, even small ones. The document is short and it prevents most of what goes wrong later.
- Handover is designed in from the beginning, not bolted on at the end. We would rather be kept than be difficult to leave.
- We say no to work we would do badly. The list of things we do not do is published on every capability page.
Direction
Where this is going.
Patterns repeat. The fee structure a school needs is a variation on the fee structure the last school needed; the intake pipeline for one document type is most of the pipeline for the next. Where a build has proved itself across several organisations, we are packaging it into a configurable system that can be deployed and adapted rather than written again from scratch.
That is a slow, deliberate transition and we are not going to pretend it has already happened. Today the work is bespoke, and the packaged versions are being extracted from real deployments rather than designed in advance — which is the only way they end up fitting anybody.
Next step
Ask us something specific.
The fastest way to work out whether we are any good is to send a real problem and read what comes back.