TechPerLab is a product lab. Our core work is simplifying the needs we observe in the field and turning them into software products. Alongside that we build custom solutions too, and we use the same working discipline in custom work. This post is about the way of working behind “from idea to product, from product to impact.”
Why aren’t we tied to a single industry?
Our portfolio today holds a legal workflow product (Vekilya), an appointment tracking product (Bildirgo), and an inventory and orders product (Sevkora). What could a law firm and a warehouse, a person waiting for an appointment and a team counting stock, possibly have in common?
What they have in common is the shape of the problem. In all three, information is scattered, responsibility is unclear, and the current state of the work is not visible enough. The industries differ; the shape of the friction is strikingly similar. We focus on the forms of friction that repeat across different industries. So if a need from an entirely different field comes to us tomorrow, we put it through the same filter. We look at the need, at what it looks like in everyday operations, and at how a simple product could resolve it.
Same friction, different scene
In the firm Vekilya is built for, deadline tracking usually runs in the lawyer’s head rather than in a system; as the number of files grows, tracking that with memory alone gets harder. In the warehouse Sevkora is built for, the same friction appears in another scene: the number in the record and the number on the shelf drift apart over time, because recording gets separated from the moment the work happens. For the user Bildirgo is built for, the essence is the same: when an available appointment slot will open is unknown, and that uncertainty turns into the habit of checking the same page over and over during the day.
The three scenes look far apart; a law firm, a warehouse, and a user waiting for an appointment are not in the same industry. But the shape of the friction is the same: information is out of reach at the moment the work needs it most, and memory or persistence has to cover the gap.
Same discipline, different product
Because of that shared shape, we put all three products through the same filter: first we observed the problem as it is, then we reduced it to a single core. In Vekilya the core is making it visible at a glance which deadline is running on which file. In Sevkora the core is being able to record a stock movement as it happens, so the number on the shelf and the number in the record stay the same. In Bildirgo the core is taking the availability check out of the user’s hands, making it automatic at regular intervals, and sending a notification when a slot opens.
We set the scope of each product around its essential need. In Vekilya, legal assessment and decisions belong to the lawyer; the product only organises the workflow. Sevkora stays on a simple and focused line for trading and distribution businesses. In Bildirgo, an appointment happens with the user’s explicit approval at that moment. These boundaries are deliberate choices about scope.
We describe the steps of this approach in detail on the how we work page; what we wanted to pass on here is how the same working discipline is applied to different products.
What you will find on this blog
Industry observations analysing the everyday friction of different fields, practical guides on business processes, notes from the lab on our product development process, and approach pieces on the way we work. Our priority is describing the problem itself accurately; we believe that is the best introduction there is.
If you have a question about one of our products, you can write to us from the contact page.