Work directly withDevelopers
The person who scopes your project is the person who writes it.
Simnetiq is two owner-operators. There is no account manager between you and the code, no sales engineer who disappears after the pitch, and no junior team the work is quietly handed to once the contract is signed. You brief the person who builds it, and you keep briefing that person until the project ships.
In practice
What this means
At a glance
Who you actually talk to
Simnetiq Ltd is registered in England and Wales (Companies House 16861177) and run by two directors. Roman Pochtman handles engineering — mobile, web, AI and infrastructure. David Zitomirsky handles contracts, compliance and finance. On a technical call you are talking to Roman. On a contract question you are talking to David. Nobody is relaying messages between you and a delivery team, because there is no delivery team to relay them to.
Why this changes the estimate
When the person estimating the work is the person who has to do it, the estimate stops being a sales number. There is no incentive to quote optimistically to win the deal and absorb the overrun later, because the overrun lands on the same desk. It also removes an entire category of defect: the requirement that gets lost between the person who heard it on the call and the person who implements it three weeks later.
What this costs you
Bandwidth. Two people cannot run six engagements at once, so we take fewer projects and start dates are a real constraint rather than a formality. If we are booked until a given month, we say so and give you the date. We would rather lose the work than start it and stall.
The bus factor, stated plainly
A two-person studio carries a continuity risk that a fifty-person agency does not, and pretending otherwise would be dishonest. The mitigation is not a promise that nothing will happen. It is that nothing we hold is unrecoverable if it does: source sits in your repository, infrastructure sits in your accounts, and deployment is documented well enough for an engineer who has never met us to take it over. That is a deliberate design constraint on every engagement, not a courtesy at the end of one.
Questions
Common questions
Will the work be handed to a junior developer after I sign?
No. There is no junior team to hand it to. Simnetiq has two directors and the engineering is done by the director who scoped your project.
Can I speak to the engineer before there is a contract?
Yes. Scoping calls are with the engineer, not a salesperson, and they happen before there is anything to sign. That call is also where you find out if we are the wrong fit — we would rather say so early.
How quickly do you respond during a project?
Within one working day for anything routine, and the same day for anything blocking a release. We work UK hours from London and correspond in English, Hebrew or Russian.
What happens if you become unavailable mid-project?
Your repository, your infrastructure accounts and your deployment documentation are already in your hands, so another engineer can continue without our involvement. We would also tell you early rather than let a deadline pass quietly.
How many projects do you run at the same time?
Deliberately few. The exact number depends on the size of each engagement, but the constraint is real and it is why we quote start dates rather than starting immediately.
Contact Us
Still have a question?
Ask it before you commit to anything. Briefs and questions are answered within one working day, by the engineer who would do the work.