Engineers who stand behind
what they hand over.
A small team with no layer of managers. We take on what we do well and say “no” to the rest. The client gets all of it: code, access, rights.
Three things
we don't compromise on.
A working screen instead of a promise
A demo every 2–3 days. The gap between what you meant and what we understood surfaces in the second week and costs hours. At handover the same gap would cost weeks.
We understand every line we hand over
Every line goes through review by a person. If an engineer cannot explain why a solution works, it does not go into the project. That is slower and more expensive. We have found no other way to keep a system maintainable a year later.
Nothing ties you to us
The source code, the infrastructure and the rights are yours under the contract. A good contractor is one you can walk away from in a day. We would rather you did not want to.
Four rules
the work runs by.
Speed
The first demo on day 3–5. A working screen is easier to discuss than a promise.
Transparency
An estimate broken down line by line, access to the repository from day one, a weekly report with the risks. Bad news comes from us, early.
Security
A dependency check on every project, and an audit before launch on the ones that involve money or personal data.
Code ownership
The source code and the rights are yours. You can walk away from a good contractor in a day, and that is how it should be.
Who does the work
and what they answer for.
Below are roles. We do not publish names and photographs yet, so the team is shown this way.
Lead engineer
Architecture, backend, code sign-off
Answers for the system holding up under load and for it still being maintainable a year from now. Reviews every merge and has the right to say “this is not going out”.
Front-end engineer
Interfaces, accessibility, performance
Counts Core Web Vitals as part of acceptance, the same as buttons that work. Checks every screen from the keyboard and at 320 px.
AI engineer
Agents, knowledge bases, quality evaluation
Builds agents and measures them on labelled datasets. Reckons 80% of answer quality comes from the knowledge base and only the remainder from the choice of model.
Security engineer
Penetration testing, AI red teaming, compliance
Breaks colleagues' work before an outsider gets the chance. Maintains an internal catalogue of attacks on LLM agents.
How we got here
without a garage origin story.
- 2025
First projects as a team
We put together a small team of senior engineers and our own library of standard blocks: authentication, payments, an admin panel. We measured that rebuilding them from scratch on every project is the most expensive habit in the industry.
- Early 2026
IT&SOFT as an agency
We formalised the practice: a brief with the economics worked out, a demo every 2–3 days, mandatory review of every line by a person.
- Spring 2026
AI red teaming lab
We built a test rig with a catalogue of attacks on LLM agents. We run our own rollouts through it before handing them to the client.
- Now
Voice agents and digital twins
Two areas in progress: voice where it is easier for the customer to speak, and simulation where a decision is too expensive to test on a live business.
Work with us
or join us.
Tell us about the task and we reply within two hours. Or look at the open roles if you would rather be on our side of the table.