The Third Option for Founders
Agencies are slow and expensive. Freelancers make you the project manager — so we built one accountable team, priced for startups.
Why “Sakura”
Cherry blossoms bloom exactly when they're ready. We launch products the same way — on time, and genuinely ready.
Who We Work With
Founders building a real product, and teams whose processes outgrew spreadsheets. One team from idea to launch — or to automate the manual work.
Track record
100+ Projects in 30 Countries
No office, no borders. Hover a country to see how many clients we've worked with there.
- 100+
- Projects delivered
- 77
- Clients
- 30
- Countries
Since 2020, across every service we offer.
Most of them came back for a second project.
Five continents, one distributed team.
How We're Structured
A core team of 24 plus specialists per discipline. Senior people on your project — not a junior after the sales call.
A Global, Remote-First Team
Our team works across time zones, so projects keep moving overnight. That's how we've worked with clients in 30 countries.
The team
24 People, One Accountable Team
Every discipline in-house, nothing subcontracted. These are the leads you'll actually talk to.
Vladimir Kurilo
Co-Founder, Product & Business
Ivan Savsuik
Co-Founder, Product & Design
Gleb Sosnovskiy
Tech Lead
Max Kurilo
Design Lead
How the 24 split up
- Engineering
- 7
- Product Design
- 5
- Brand & Motion
- 3
- SEO & Content
- 3
- Marketing
- 3
- AI & Automation
- 3
Know Someone Building Something?
They get 10% off their project. You earn 10% of what they pay — with no cap.
Get your referral codeWe're Always Hiring
Design, engineering, SEO, motion, and automation roles are open. Not listed but great at what you do? Send your work anyway.
See open rolesWorking since 2020
6 Years of Shipping, Not Pitching
Running since 2020. The process on this page is what we do, not what we plan to do.
2020
Three people, one rule
Sakura starts as a design-and-build duo plus a developer, with a single rule: one accountable team per project, never a relay of freelancers.
2021
Development in-house
Engineering moves in-house so design hand-offs stop being someone else's problem. First clients outside Europe sign on.
2022
Remote-first by default
The team goes fully distributed across time zones — async updates and weekly checkpoints become the standard process, not an exception.
2023
Growth joins the scope
Launch stops being the finish line. Retainers for SEO and marketing turn one-off builds into multi-year client relationships.
2024
AI automation practice
A dedicated practice for custom agents and workflow automation, built for teams drowning in work that shouldn't be manual.
2026
Where we are now
Six years in: 100+ projects shipped, clients on five continents, and the same rule the first three people started with.
How We're Different
Accountability, speed, pricing, and process — side by side.
Corporate agency
Slow and expensive
- Accountability lost in account layers
- Slow, bureaucratic approvals
- High, rigid pricing
- Opaque process
Sakura
Fast and accountable
- One team, one contact
- Fast, structured delivery
- Scoped, fixed price
- Documented, weekly process
Freelancers
Cheap but fragile
- You're the project manager
- Fast until someone drops out
- Low, unpredictable pricing
- Improvised process
Our Process
No improvising, no black box. Here's exactly what happens, step by step.
- 1
Brief
Tell us what you're building, for whom, and why. 15–30 minutes, async or on a call.
You provide: Goals, rough scope, any existing materials.
You get: A same-week response with initial questions or a proposal date.
- 2
Proposal
We turn your brief into a fixed scope, timeline, and quote. You know the price before work starts.
You provide: Answers to any scoping questions.
You get: A written proposal with deliverables, milestones, and price.
- 3
Design & Build
Weekly cycles you can see, not one big reveal at the end. Design and development run in parallel.
You provide: Feedback at each checkpoint (usually weekly).
You get: A live staging link updated as we build, not static decks.
- 4
Launch
QA, performance checks, and a go-live checklist. SEO, analytics, and monitoring are ready before launch.
You provide: Final sign-off.
You get: A launched product, plus a handoff doc covering everything we built.
- 5
Grow
Launch is where real data starts. SEO and marketing keep going based on how users actually behave.
You provide: Ongoing goals as they evolve.
You get: Monthly reporting and a standing plan for what's next.
How Pricing Works
No price list — on purpose. A landing page and a marketplace shouldn't cost the same.
Why We Don't Publish a Price List
- Corporate agencies quote high to cover overhead you're not using.
- Freelancer rates look cheap until scope creep multiplies the hours.
- We quote the actual scope, once, so the number doesn't move later.
Most proposals go out within 2–3 business days of a brief — see the process.
What Affects Your Quote
- Scope and number of features
- Design complexity and number of screens
- Third-party integrations (payments, auth, data)
- Timeline — standard vs. expedited delivery
- Whether you need ongoing support or growth work post-launch
FAQ
Process & Timeline
We re-scope the affected piece and tell you the cost and timeline impact before proceeding — never a surprise on the final invoice.
Async updates by default, plus calls in overlapping hours scheduled around your time zone. Our own team is distributed, so this is how we always work.
Revisions are built into every stage — we'd rather adjust early than have you discover it at delivery.
Pricing & Payment
We're set up for early-stage builds, not enterprise minimums — tell us your scope and we'll tell you honestly if we're the right fit.
Yes, a portion upfront to begin, with the remainder tied to milestones — never 100% before work starts.
Yes — this is the default structure, not an exception.
Tell us the number. We'll either scope a version that fits it or tell you directly if it's not enough for what you're describing — no false promises either way.
Yes, for SEO, marketing, and continued development — scoped separately once you know what post-launch support you need.