Start with the operation.
We examine who does the work, where information comes from, what can go wrong and which exceptions the software must handle.
Mihail Istilyanov · Product and software lead
A software partner who can move from business problem to working product.
Istilyanov is a Mihail-led software practice for established businesses that have outgrown spreadsheets, disconnected tools or generic products.
Experience across product and technology
Mihail works across the whole product, not only one technical layer.
Mihail's background spans enterprise platforms and Salesforce ecosystems, websites, web and mobile products, workflow automation, integrations and technical advisory work. A website problem can quickly become a payments, data, mobile or internal-workflow problem.
Direct accountability
The person making the product decisions stays close to delivery.
Mihail leads the work from the first workflow conversation through product definition and technical direction. That keeps business trade-offs, customer experience and engineering decisions connected instead of handing the problem between separate sales, strategy and delivery teams.
Relevant specialists can join where they improve the outcome, but the responsibility for making the system useful remains clear. The goal is practical software that the team can understand, maintain and use after the first release.
See how the work is shaped →Working principles
What you can expect when the work gets complicated.
Challenge the proposed solution.
A responsible partner should say when a feature, a platform or the entire custom build is unnecessary.
Keep accountability close.
The person defining the system should stay close to the decisions, the trade-offs and the delivery.
Build for the day after launch.
The result should remain understandable, maintainable and useful after the initial release.
Start with the reality of the business