Skip to content
olrik
Selected work

What we changed, how we changed it, and what it was worth.

Client names sit under NDA, so we publish the part that actually helps you evaluate us: the constraint, the architecture, and the numbers before and after.

Discuss a similar projectSee capabilities

Across the engagements below

5
Engagements detailed
across four sectors
7.4
Average weeks to launch
concept to production
100%
Handed over in full
code, infra, documentation
0
Rewrites required
post-handover
SaaS2025

Cut support load by 62% without adding a single agent

A support team of nine was drowning in 4,200 tickets a month, two thirds of which were answered somewhere in the documentation. We built a grounded assistant that resolves them and escalates cleanly when it should not.

62%
Tickets deflected
90s
Median first response
6 weeks engagementCase study
Marketplace2025

Re-architected a platform that collapsed above 5,000 concurrent users

Peak traffic was taking the marketplace down every campaign day. We rebuilt the data and caching layers, cut p95 latency by 88%, and took it to 80,000 concurrent users on a smaller infrastructure bill.

210ms
p95 latency
80k
Concurrent users
11 weeks engagementCase study
Healthcare2025

Automated claims intake and reclaimed 20 hours a week

Four coordinators spent their mornings retyping referral documents into the practice management system. We built a document pipeline that extracts, validates, and files them — with a review queue for anything it is not sure about.

20 hrs
Reclaimed weekly
99.2%
Field-level accuracy
7 weeks engagementCase study
Fintech2024

Closed 31 findings and passed audit with zero criticals

A payments company had eight weeks before an audit and a security questionnaire from an enterprise prospect stalled on their desk. We threat-modelled the platform, fixed what was exploitable, and moved the checks into their pipeline.

0
Critical findings
31
Findings remediated
8 weeks engagementCase study
E-commerce2025

Connected 38 systems and removed 1,900 manual hours a year

Order, inventory, fulfilment, and finance data lived in six systems that only agreed with each other because someone reconciled them by hand every night. We replaced that person with infrastructure.

1,900
Hours removed
0.1%
Oversell rate
5 weeks engagementCase study

Note: engagements are described without identifying details at our clients’ request. On a call we can usually arrange a reference conversation with a past client working in a comparable domain.

Let us look at your architecture.

Two ways to start, both of them short. Bring the problem, not a specification — the first useful thing we do is tell you what we would build and roughly what it costs.

Book an architecture call

Fifteen minutes, no deck. We map your problem to an approach and tell you what a realistic scope and budget look like.

  • A specific technical recommendation
  • A budget band you can plan against
  • An honest answer if we are the wrong fit
See available times

Send a written brief

Prefer to write it down? Email us the shape of the problem and we will reply with a first take, usually under 12 hours.

  • Goes straight to an engineer, not a sales inbox
  • We reply with an approach, not a brochure
  • Attach anything: repos, docs, screenshots
hello@folrik.com