Product assistant
External development without lock-in
It's the most reasonable fear when hiring external development: that the day the team leaves, the product's knowledge leaves with it. And it's not paranoia - a good part of the industry lives precisely off you depending on the supplier.
We've built the opposite: every product we develop ships with an assistant that knows it. And that keeps working when we're gone.
The usual trap of external development
It's not bad luck: it's the business model of part of the industry. These four scenes repeat in almost every bad experience with outsourced development:
- When the external team leaves, nobody knows why things are built the way they are
- A new developer takes weeks to get up to speed
- Every how-does-this-work question means going back to the original supplier
- And the supplier has an incentive to keep it that way: dependency bills
How we solve it
While we develop, we document the architecture decisions, the data structure, the why behind each choice and how it's deployed. On top of that documentation we build a conversational assistant that answers questions about your specific product - not about programming in general: about yours. That's the whole trick, and it's why it works: without living documentation underneath, no assistant is worth anything. And it updates sprint by sprint, not at the end - which is why it never goes stale.
What it's for, concretely
- Getting a new developer up to speed without depending on us
- Resolving how-does-this-work questions without opening a ticket
- Understanding why a technical decision was made eight months ago, without email archaeology
It stays with you. Literally.
The assistant and the documentation run on your Azure subscription, not ours. They're not a Vettra subscription that gets cut off the day you stop paying us: they're a piece of your product, as much yours as the code.
If tomorrow you reduce dedication, change supplier or build your own team, everything stays in place: the documentation, the assistant and the answers. Nobody has to call us to find out why something is built the way it is.
Compare it with the usual: a repository handed over without context and a maintenance contract as the only way to get questions answered. The difference isn't visible on delivery day - it's visible the first day you need to change something without us.
Our declared goal is for you to stop needing us. That's not website copy: this is the piece that makes it verifiable.
What it doesn't do
It doesn't write code, fix bugs or make decisions. It doesn't replace a developer or a CTO: it prepares and explains, and people decide. If someone sells you otherwise, be suspicious.
When you don't need this
If your product is built by your own stable team that documents with discipline, this adds little: the knowledge already lives in-house. And if you're looking for the assistant on its own, without development, we're not your supplier either - we don't sell it separately. Where it changes things is when development is external or the team rotates: that's where knowledge tends to evaporate.
What it costs
It has no price of its own because it isn't sold separately: it's included in every development, like the documentation and the QA. What development costs - with public prices, like everything here - is on software development.
Frequently asked questions
Nothing: the documentation is yours from day one and the assistant runs on your Azure subscription, so it keeps answering just the same. It's part of the exit plan, not a service that switches off.
It can, but not out of the box: the assistant answers over documentation that exists. With an inherited product, it first needs auditing and documenting - work we also do - and on that base it can be built. Without it, it would be a generator of pretty, unreliable answers, and we'd rather tell you.
You do, directly to Microsoft: the services run on your Azure subscription, with no margin of ours and no Vettra fee. That also makes it clear whose it is.
What we generate during development: architecture decisions and their why, data structure, how it's deployed and how the product has evolved sprint by sprint. In a queryable format - not a farewell PDF.
Does the lock-in story sound familiar?
Tell us - even if someone else built your product. We reply within one business day with an honest read of your case.