About
A small team with strong opinions — and the receipts to back them.
Wrenq is an independent software studio. We've spent years inside healthcare platforms, AI voice systems, and property management software — long enough to know which patterns survive contact with real users, and which ones quietly rot.
What we believe
Six principles, no slogans.
We'd rather be the team you hire twice than the one you over-promise with once. These are the working agreements that get us there.
Small team, big opinions
We're a senior crew of a few — not a body shop. The engineer you talk to is the engineer who writes the code, owns the trade-offs, and stays around when the product ships.
AI-native by default
AI is woven through the way we build and the products we build — copilots, voice agents, evals, and tool-calling. Not bolted on for a demo.
Domain-Driven Design as a habit
We model the business before we model the database. Bounded contexts, ubiquitous language, anti-corruption layers — applied with judgment, not as ceremony.
Sprints you can plan around
We work in 2 to 4 week sprints. The sprint cadence and demo schedule are agreed in writing before the first commit, so your stakeholders know exactly when to show up and what they'll see.
We work in your timezone
Communication beats heroics. We align our working hours to your team's timezone so reviews and demos happen during your day — not as overnight catch-up.
Calm shipping
Steady weekly demos beat heroic crunches. The product gets there, and we're still around to maintain it.
How we work
The way an engagement actually runs.
We're explicit about cadence and communication so the surprises stay in the product, not the process.
AI is a feature, not a layer
We use LLMs where they earn their keep — voice receptionists, copilots, evals — and we measure them like any other dependency.
DDD beats CRUD-with-extras
Most production pain comes from a missing model. We invest in the domain early so refactors stay small and additions stay cheap.
Predictable cadence
Sprint dates, demo dates, and release dates are agreed before kickoff. No surprise scope, no surprise invoices.
Your timezone, your hours
We adjust our working hours and demo windows to overlap with your team — wherever you are.
Engagements
How working with us looks.
- Discovery (1–2 weeks). We scope the problem, sketch the architecture, and produce a written sprint plan — sprint length (2–4 weeks), demo dates, release dates, and the working-hours overlap with your team.
- Build phase. Sprints run on the schedule we agreed. Demos at the dates we agreed. Shared backlog, no surprise scope, no surprise invoices.
- Maintain & evolve. Optional ongoing retainer for the inevitable next thing.
Legal & billing
Straightforward billing.
Sergiy Bondarev
IČO: 23604280
Bachmačská 691, 280 02 Kolín — Kolín II, Czech Republic
Zapsán v živnostenském rejstříku, Městský úřad Kolín
Full disclosure on the imprint page.