How we work
The rhythm you can set your calendar by.
Nobody publishes how they actually run an engagement, so here is ours, in enough detail to hold us to it.
- Sprint
- 2 weeks
- Demo
- Every sprint
- Status
- Weekly
- Lead
- Named
Our operating rhythm
Discovery before a quote
We map the workflow, the data model and the constraints before putting a number on the work. A quote written without that is a guess with a decimal point on it.
Fixed price, and yours whether or not we build.
Two-week sprints
The work is planned, built and closed in two-week increments. Scope for the sprint is agreed at the start of it, and what is in it does not change halfway through.
Sprint goal agreed in writing.
A demo every sprint
You see the system running at the end of every sprint, on real data, driven by us. Not a slide about progress, the software itself.
Recorded, so people who missed it can watch it.
A written weekly status
Four headings, every week: what progressed, what is next, what the risks are, and what is blocked. Short enough to read, specific enough to act on.
Progress · Next · Risks · Blockers.
One named engagement lead
One person who owns the relationship, knows the whole system, and answers for it. Not a rotating account manager between you and the engineers.
Named at kickoff, and for the length of the engagement.
Change control in writing
New scope gets a written impact on cost and date before it enters a sprint. Scope moves deliberately, or it does not move.
Nothing enters the build on a verbal yes.
Five stages, run in order.
The rhythm above is how each week feels. This is the shape of the whole engagement: the decisions that are expensive to reverse get made early, and deliberately.
- 01
Understand
Business, users, workflows, constraints.
We map how the organisation actually runs before proposing anything, including the parts that live in spreadsheets, habits and people's heads.
- Workflow map
- Constraints
- Success criteria
- 02
Architect
System architecture and technical direction.
Data model, system boundaries, integration points and the failure cases. The decisions that are expensive to reverse get made here, deliberately.
- Data model
- System design
- Integration plan
- 03
Design
Product experience and workflows.
Interfaces designed against real data volumes and real roles, so the product holds up when it leaves the demo.
- Interface design
- Workflow design
- Design system
- 04
Build
Engineering, testing, integration.
Built in working increments with a demo every week. You see the system running throughout, not at the end.
- Working increments
- Weekly demos
- Test coverage
- 05
Launch
Deployment, monitoring, iteration.
Deployment, monitoring and the first weeks in production, where a system proves whether it was engineered or assembled.
- Deployment
- Monitoring
- Iteration
Three ways to start with us.
Structures rather than rates, so you can work out which one you are before the call rather than during it.
Discovery
Two to three weeks, fixed price
We map the workflow, the data model and the constraints, then come back with an architecture, a first milestone and where we think the risk sits. It stands on its own: the output is yours whether or not we build it.
Start here when the problem is clear but the shape of the answer is not.
Fixed-price build
Scoped and quoted before engineering starts
You know what is being built and what it costs up front. Two-week sprints, a working demo at the end of each, a written weekly status, and change control in writing so scope moves deliberately rather than quietly.
The default for a defined system with a date attached to it.
Retainer
A standing monthly capacity
For systems already in production: iteration, regulatory change, new integrations, monitoring and the on-call reality of running software. A named engagement lead, and a backlog you set the order of.
After launch, or for a system you already own and need kept moving.
Things people ask us first.
What kind of software company is Solinovo?
Solinovo builds the operational and compliance systems established companies depend on. We are based in Lahore, Pakistan and work with clients worldwide. We build business systems and ERP, applied AI and automation, data platforms and statutory integration, and we design, ship and operate our own products, starting with Quick Safa.
What does Solinovo specialise in?
Four disciplines, deliberately: business systems and ERP, including double-entry accounting, inventory, production and costing; applied AI and automation grounded in a client's own records, with a person reviewing and signing the output; data and analytics, including warehouses, dimensional models and plain-English querying; and integration with statutory compliance, including FBR digital invoicing. Web and mobile are how these are delivered, not separate services.
Do you build accounting and ERP software?
Yes, and we run our own. Quick Safa is a Solinovo product in production: a double-entry general ledger with inventory, purchasing, sales, production planning, a board costing engine and FBR digital invoicing built in. Operating it ourselves is why we argue about data models before anyone writes code.
How do you price and scope a project?
Three structures: a fixed-price discovery of two to three weeks, a fixed-price build scoped and quoted before engineering starts, and a monthly retainer for systems already in production. On a build you know what is being built and what it costs up front, you see a working demo every sprint, and the code, accounts and infrastructure are in your name from day one.
How long does a typical project take?
The projects on this site ran between five and ten weeks. The real answer depends on how much of the problem is already understood, we come back with an architecture, a first milestone and where we think the risk sits, usually within a couple of days of the first conversation.
Do you work with international clients?
Yes. We work with clients worldwide, and several of the case studies on this site were delivered for organisations abroad. Engagements run remotely, with roughly four hours of daily overlap with Central European working hours and with North American mornings, a working demo every sprint and a written weekly status.
Will AI be making decisions in my business?
Not unless you want it to. The system drafts and the specialist signs. A clinician signs the report, a rep sends the email, an operator releases the job, and every automated output that carries consequence has a named human owner. Where an agent does act autonomously, its answers are grounded in your own records and cite the source they came from.
How do you handle our data and our intellectual property?
Devices are encrypted and every account takes a second factor. Production data never goes onto a developer machine; development and testing run on anonymised or synthetic records. Each client gets a separate environment with separate credentials. An NDA is signed as standard before the first technical conversation, and the intellectual property transfers to you on payment, with code, cloud accounts and domains in your name from day one.
What happens after launch?
We stay. Production responsibility doesn't transfer the moment something ships. Deployment, monitoring, backups, migrations and regulatory changes are part of the engagement, not a separate conversation.
Next step
Start with a discovery.
Two to three weeks, fixed price, and the output is yours whether or not we build the thing afterwards.
Direct
contact@solinovo.comWe reply within one business day. If we're not the right fit, we'll say so.