How we work
From problem to solution, in twelve steps.
The same process, applied consistently — on client projects and on our own products (eSRL, 1002, Pinyap).
Discovery
We understand the current process, who runs it, and what works and what doesn’t — straight from the team that works with it daily, not just from management.
Deliverable: A written summary of the process, goals and constraints.
Process analysis
We map the flow step by step, identify the real bottlenecks, and separate what’s truly a problem from what’s just a habit.
Deliverable: A process map with the bottlenecks identified.
Goals
We explicitly define what success means for this project — time saved, fewer errors, a trackable process — so we can later verify whether we succeeded.
Deliverable: Goals and success criteria, agreed in writing.
Prioritization
We don’t solve everything at once. We identify what brings the most impact for the least risk, as the first deliverable stage.
Deliverable: A prioritized backlog and delivery phasing.
Architecture
We choose the technical approach — custom software, automation, integration, AI, or a combination — with the trade-offs stated explicitly, not hidden.
Deliverable: An architecture diagram and the technical decisions, with their rationale.
MVP
We build a first usable version, with just enough scope to be tested in real conditions — not the whole system at once.
Deliverable: A working version, testable under real conditions.
Testing
We verify functionally and with real users before launch — we don’t assume it "works", we confirm it.
Deliverable: Acceptance criteria and testing results.
Security
Role-based authentication, server-side validation, data separation — reviewed before launch, not bolted on afterward under pressure.
Deliverable: A security review, sized to the project’s risks.
Launch
We launch in a controlled way, with a rollback option, not as a single irreversible event.
Deliverable: A deployment plan and a rollback plan.
Monitoring
Uptime, errors and performance are actively tracked after launch, with alerting — we don’t hear about problems from users first.
Deliverable: Metrics, logs and alerting set up.
Maintenance
Ongoing security updates, fixes and optimizations (see also maintenance & infrastructure) — a system launched and abandoned becomes a risk.
Deliverable: A support and evolution plan for the system.
Change management
Requirements evolve. We handle later change requests in a structured way — evaluated, prioritized and integrated, not bolted on ad hoc to a system that wasn’t designed for them.
Deliverable: An agreed process for evaluating, approving and integrating changes.
Who does what
What Leadpro provides
Analysis, justified technical decisions, development, testing, documentation and the deliverables defined at each stage above.
What the client provides
Access to the real process and the people who run it, timely decisions on points that need approval, and access to the relevant existing systems.
Who signs off
Every stage with a deliverable is explicitly signed off by a designated point of contact on the client side before moving to the next stage.
How changes get approved
Any new requirement that comes up along the way goes through step 12 — evaluated, prioritized and integrated in a structured way, not implemented ad hoc.
Ways of working together
The collaboration model follows from how the problem is assessed.
It’s set after assessing the problem, the project’s maturity, and the level of involvement needed — no fixed prices listed here, but the concrete working formats below.
Starting out
Paid discovery
We analyze the process and recommend a technical direction, as a separate stage, before committing the budget for full development.
Fixed-scope project
A clear goal, with budget and timeline set from the start — a good fit when the problem is already well understood.
MVP
We build a minimal first version, quickly testable, to validate the direction before investing in the whole system.
Ongoing development
Incremental development
Phased deliveries, each one usable, instead of a single large deliverable at the end of the project.
Extended team
Integrating as an extension of the internal technical team, for a project or a defined period.
Hourly support
For one-off interventions, with no long-term commitment.
Operation & evolution
Maintenance subscription
Ongoing updates, monitoring and fixes for a system already in production.
Continuous operation
Just like with our own products — we stay responsible for the system indefinitely, not just until launch.