The team you meet is the team that builds it
No swapping in juniors once the contract is signed.
Software studio · Wrocław, Poland
Every studio says it delivers on time and tells the truth about problems. Saying it costs nothing. So we've written our commitments down as a ledger you can read, countersign and hold us to — right below, before you've spent a złoty.
Wrocław, Stare Miasto
Small, senior, no handoffs
One business day
01 / The ledger
These are the terms we hold ourselves to on every engagement. Countersign any entry to timestamp it — the same way you'd initial a line in a ledger before agreeing to it.
No swapping in juniors once the contract is signed.
If something slips, you hear it at the weekly demo — not on the final invoice.
Documented, conventional, handed over in full — no dependency on us to read it.
What's in and what's explicitly out, agreed in writing, so "out of scope" is never a surprise.
You'll hear that on the first call rather than three sprints in.
Monitoring, fixes and the next round of improvements. Release day is a checkpoint, not an exit.
02 / Services
Not a catalogue of everything possible — these are the areas we've shipped in repeatedly and are willing to be measured on.
Native iOS and Android, plus React Native and Flutter where a shared codebase genuinely serves the product rather than just the estimate.
Dashboards, client portals and SaaS products on React, Next.js and Node — tuned to stay quick on an average phone, not just a dev machine.
Research, clickable prototypes and design systems that keep their logic once a few years of features have piled on top.
APIs, data models and infrastructure on AWS or GCP, scaled to the traffic you expect — with a written plan for the traffic you don't.
Payments, ERP, CRM and logistics systems wired together properly, plus automation for the manual steps your team keeps repeating.
CI/CD, monitoring, and a named person who picks up when something breaks outside office hours.
03 / Sectors
Each of these carries its own constraints — compliance, uptime, seasonal load. Knowing them upfront is most of an honest estimate.
Reporting, analytics and onboarding flows with an audit trail.
Fleet visibility, route planning and driver apps built for poor coverage.
Storefronts, loyalty mechanics and stock synchronisation across channels.
Booking systems, client portals and internal tools that replace spreadsheets.
04 / Process
The same rhythm on every engagement, so there's never a fortnight where you're guessing what your budget is doing.
We map users, constraints and risks, then write down what's in and what is explicitly out before any code exists.
Sketches become clickable prototypes and get tested while changing direction still costs nothing.
Two-week sprints, a live demo at the end of each, automated tests running the whole way through.
Store submission or production deploy, analytics connected, then iteration based on real usage.
05 / Studio
TRUS SP Z O O is a software studio registered in Wrocław. We work with founders and in-house teams who want the people writing the code to also understand why it's being written.
Staying small is a constraint we chose, not a phase we're trying to outgrow. Every project gets senior attention, decisions take hours rather than weeks, and nobody is learning your domain at your expense.
A commitment you can point back to is worth more than any number of case studies.
That's the reasoning behind the ledger at the top of this page. Most studios put their promises in a proposal that nobody reads twice. We'd rather publish ours where a prospective client can read them before the first call — and where an existing one can hold them up mid-project.
If any entry there doesn't match how we've actually worked with you, say so. That's the point of writing them down.
06 / Contact
Call, or send a short brief below. You'll get initial questions and a rough shape of the work within one business day.