We started Guessyou Limited because the agencies we'd worked at were optimised for billing, not building. We wanted a place where senior engineers stayed on the keyboard, where scope was a conversation not a contract, and where the work could be evaluated by anyone in the room.
Guessyou Limited started in 2022 with a rule: every project must end with a working product or a written reason why it didn't.
Grown carefully since then — adding people who could be trusted in front of a client without supervision, turning down work that didn't fit, and writing down our process as we discovered it. The studio is still small. That is on purpose. We take a handful of new engagements each quarter, scope them tightly at the start, and grow them only when the fit is obvious.
The company doesn't have a sales team. The person who picks up your first email is the person who'll sit in your first demo. If that sounds inefficient — it is. It's also why we sleep at night.
Founder MVP
For non-technical founders, the first sprint turns product ambition into a scoped backlog, clickable prototype, and working slice that can be judged before a larger build.
What you can inspect: discovery brief, prototype, first production workflow, and handover notes.
Product team capacity
For product and engineering teams, we take a contained feature, integration, or platform track and run it with shared repos, demos, and written decisions.
What you can inspect: milestone plan, pull requests, demo notes, tests, and release checklist.
Stability work
For teams carrying technical risk, we focus a short engagement on tests, observability, deployment confidence, and the highest-cost defects.
What you can inspect: risk register, test coverage plan, runbook updates, and prioritized fixes.
We write proposals, RFCs, and bug reports in sentences. Code is for computers; language is for people.
Whoever talks to you in discovery is whoever ships. No layered handoff to a junior nobody told you about.
If it wasn't written down it didn't happen. Architecture, scope changes, postmortems — all logged.
Postgres, REST, server-rendered HTML. We use exciting tools only where they earn their seat.
Every engagement starts with a way to end it cleanly. Trust grows from there.
We keep the team page light by design. Once you start a conversation, you'll meet the specific people who'd be on your project, see their relevant work, and know who owns each part of delivery before a paid sprint begins. We share the company details needed for vendor review during contracting; photos and bios go public only when the team wants them there.
* Counts current as of May 2026. We update them when something changes, not on a calendar.