How we work
Every RubyPlius engagement follows the same path: understand the problem, agree on a written scope, deliver in short iterations, and hand over cleanly. You see working software early and know what each step costs.
Our delivery process, step by step
The process has five steps, and each one ends with a concrete output you can review before deciding to continue.
- 01
Discovery
A call to understand the problem, users, constraints and timeline.
Output: notes + next steps - 02
Scope & estimate
Goals, scope, acceptance criteria, risks, team and an estimate.
Output: written scope - 03
First iteration
A small, real slice of the product to validate the approach.
Output: working demo - 04
Iterative delivery
Planned iterations with demos, releases and transparent reporting.
Output: releases + reports - 05
Handover & support
Documentation, knowledge transfer and optional maintenance.
Output: runbook + SLA
What happens in one iteration
Each iteration lasts two weeks and moves through planning, building, review, a demo and a release. Nothing reaches production without code review and passing CI.
Compare engagement models
Fixed-scope projects suit clear goals, dedicated teams suit ongoing products, and audits suit decisions that need facts first.
| Fixed-scope project | Dedicated team | Technical audit | |
|---|---|---|---|
| Best for | A defined product, feature set or upgrade | Ongoing product development | Deciding what to do next |
| Scope | Fixed in writing, changes by agreement | Flexible backlog you prioritise | Codebase, upgrade path or AI idea |
| Pricing | Fixed price per scope | Monthly, per engineer | Fixed fee |
| Reporting | Milestone demos | Iteration demos + weekly status | Written report + call |
Engineering and communication standards
The same baseline applies to every project, regardless of size or engagement model.
Engineering
- Code review on every pull request
- CI with automated tests and security scans
- Separate staging environment
- Infrastructure as code where we run it
- Documentation kept in the repository
Communication
- A demo at the end of every iteration
- Written weekly status: done, next, risks
- Shared Slack or Teams channel
- Your tracker: Jira, Linear or GitHub
- English or Lithuanian
Process questions
How the day-to-day collaboration works.
What happens if the scope changes?
We write down the change, estimate its impact on time and budget, and continue only after you approve it.
Who will work on our project?
A team matched to the scope, with one technical lead as your main contact. You see the team composition in the written scope.
Can we stop after the first iteration?
Yes. You keep everything delivered so far: code, documentation and the scope document.
Which time zone do you work in?
Our working hours follow Lithuanian time (EET/EEST), with overlap for clients in the EU and UK.
Start with a discovery call
Tell us about the problem; we will tell you how we would approach it.