Internal tools
The admin panel your ops team lives in. Bulk actions, audit trails and permissions that match how the org actually works, not how the org chart says it does.
Web platforms
Dashboards, portals and the internal tools your team lives in all day — modelled properly, load-tested before launch, and handed over on your own infrastructure.
8–12 weeks
Typical build
3–4 people
Squad size
from $28k
Fixed scope
What we build
Four shapes this work usually takes. Most engagements are one of them, or two that grew together.
Customer portals
Self-serve accounts, billing, documents and support — so your shared inbox stops being the product.
Dashboards & reporting
Numbers people trust. Computed once, fast at any date range, exportable without raising a ticket.
Integrations
The ERP, the CRM, the payment provider, and the two internal systems nobody wants to touch. We read the docs so you do not have to.
How we approach it
The three things we will not negotiate away, because they are what keeps the build from unravelling later.
01
Model the domain first
We write the data model before the screens. Most platform rewrites turn out to be data-model rewrites that were postponed for three years.
02
Load-test before launch
Real volumes on staging. If a report dies at 200k rows we find it in week four, not the week after go-live.
03
Boring where it counts
Postgres and a queue will carry you further than most architectures. We add moving parts only when a measurement asks for them.
What we work with
The specifics, so you can tell in ten seconds whether we cover what you need.
What we build
SaaS products
customer portals
internal tools
admin dashboards
booking systems
marketplaces
client portals
What it connects to
API development
CRM & ERP integration
payment integration
single sign-on
reporting & analytics
workflow automation
What we reach for
From the work
Fourteen clinics, one platform, one quarter
Cliniq ran scheduling across 14 sites on paper diaries and a shared mailbox. We replaced it with one platform in a quarter, and no-shows fell by a third.
See selected work →14
Clinics migrated
Questions we get
Can you take over an existing codebase?
Usually yes. We start with a week of reading and a written assessment: what is worth keeping, what is worth replacing, and what it would cost either way. You get that document whether or not you continue with us.
What about SSO, roles and audit logs?
Built in from the start rather than retrofitted. SAML or OIDC against your identity provider, role definitions you can edit yourself, and an append-only audit trail on anything that changes money or permissions.
Will it hold up at our peak?
Tell us the peak and we design to it. We load-test against real volumes on staging before launch, and we tell you the number at which the current design stops being enough.
Do you build multi-tenant SaaS platforms?
Yes. How tenants are separated — shared database, separate schemas, or fully isolated — is a week-one decision, because it changes cost, blast radius and what you can promise a customer about their data. We pick it deliberately rather than defaulting.
Can you make it accessible enough for public-sector procurement?
We build to WCAG 2.2 AA, and for anything sold into the EU, the European Accessibility Act. That means keyboard navigation, screen-reader testing and contrast checks during the build rather than a remediation project after somebody complains.
Can you automate a process that currently runs on spreadsheets?
That is a large share of what we build. We map the process as it really runs, including the exceptions people handle by memory, then replace it with something that holds the same rules — and keeps working when someone is on holiday.
Other things we do
All six services →Tell us what’s stuck.
Thirty minutes, no deck. You’ll get an honest read on scope, cost and whether we’re the right team for web platforms.
Book a call →or email hello@bytiko.com