Services / Platforms & Activation / Web Apps & Portals
Custom platforms that are actually needed — not filling every SaaS gap.
Most custom-platform wishes can be solved with existing tools. I run the buy-vs-build reality check first — and only build when custom is genuinely the right answer.
Buy-vs-build realism
I often recommend a SaaS combination over a custom build — when that's the right answer. Honestly, even when it means less revenue for me.
In-house-ready
A modern stack (Next.js, Postgres, Vercel) with documentation. Your team can keep developing after handover — no black-box build.
Tracking & performance included
Custom apps with tracking, a performance budget and SEO setup from day 1 — not as an after-the-fact migration.
What you can book
Six building blocks, individually or as a package
Audit + buy-vs-build check first. Build only when custom is truly needed.
Platform audit
Task inventory, user flows, data flows, existing stack. Output: a task map.
Buy-vs-build check
SaaS research, cost comparison (3-year TCO), differentiation requirements. Output: a decision matrix.
Tech-stack choice
Frontend (Next.js, Remix), backend (Node, Python), DB (Postgres, Supabase). Hosting concept.
MVP definition
What must be in the first version, what comes later. A clear scope boundary, documented.
Build & integration
MVP build, auth (Clerk, Supabase Auth), payment (Stripe), integrations with your CRM/shop.
Team onboarding
Code docs, architecture diagrams, Loom walkthroughs, 2–3 hands-on sessions with your dev team.
How do we differ?
Three ways to build a platform
Enterprise consultancy, classic studio or senior operator — the depth differs significantly.
| Enterprise consultancy Etribes, Cellular | App studio ACID21, Hybrid Heroes, SPRYLAB | Truong Suarez Buy-vs-build + senior hand | |
|---|---|---|---|
| Buy-vs-build discipline | Leans build (revenue bias) | Custom build by default | I recommend a SaaS combination when it fits better |
| Team size | 5–15 people / project | 3–8 people / project | Senior lead + specialised pool devs |
| Marketing connection | Rarely in scope | Rarely | Tracking, SEO, performance from day 1 |
| Price range (MVP) | €150–500k+ | €60–180k | €30–120k depending on scope |
| Best phase | Enterprise transformation | Classic app projects with a fixed team | Mid-market that couples marketing + platform |
The comparison is based on publicly available information as of 2026. If your constellation would be better served elsewhere, I'll tell you so in the intro call.
How we work
Five phases, one point of contact
Reality check first. Build only when custom is truly needed.
Audit + realism
Tasks, buy-vs-build, SaaS research. Output: a recommendation.
Concept
MVP scope, architecture, tech stack, tracking plan. Output: a requirements spec.
Build
MVP build in 2-week sprints, regular demos, early validation.
Launch
Production setup, monitoring, performance optimisation, QA.
Iteration / handover
Roadmap iteration or team handover with docs + walkthroughs.
Stack
What we work with
A modern stack that's fast and stays maintainable long-term.
Frontend
- Next.js + React
- Remix
- Tailwind + shadcn/ui
- TanStack Query
Backend / DB
- Node.js / TypeScript
- Postgres (Supabase, Neon)
- Drizzle / Prisma
- Python (FastAPI for ML/Data)
Auth / Payment
- Clerk / Supabase Auth
- Stripe / Mollie
- SSO (SAML, OIDC)
- Magic Link / Passkey
Hosting / Ops
- Vercel (EU)
- Railway / Fly.io
- Hetzner (EU self-hosting)
- GitHub Actions (CI/CD)
Recommended starting point
Two paths, depending on where you stand
Optimise an existing platform or build a new one? Both paths get a reality check.
For you if
The platform exists, the pain is growing
Tech debt is rising, editor frustration is rising, new features come slowly. Before the refactor, the reality check comes first.
7–10 days · report + 60-min call
Core Audit / Renew existing
- – Tech-debt inventory
- – Tasks-vs-tools map
- – Buy-vs-build reality per module
- – Refactor-vs-rewrite recommendation
For you if
You're building a new platform
You're starting from scratch or replacing an old custom build. You need a buy-vs-build recommendation + MVP scope + tech stack.
7–10 days · report + 60-min call
Core Audit / Build new
- – Tasks + user-flow map
- – Buy-vs-build decision with TCO
- – Tech-stack recommendation
- – MVP scope with effort
Not sure? The symptom triage on the audit page helps with the choice. The audit price is credited toward a follow-up project.
When this becomes relevant
Typical starting points
Three recurring situations where a custom platform is the right tool.
Self-service portal
Sales data across channels
How a self-service portal unifies cross-channel sales-data integrations.
Launch platform
Launching with landing pages
How custom apps connect to marketing funnels instead of stranding in a tech silo.
Relaunch
Relaunch without SEO loss
When an old platform is replaced — how rankings and tracking survive the move.
FAQ
What clients often ask before the first engagement
Buy or build — how do you decide?
Three criteria: (1) Is there a SaaS that covers > 80%? Then buy. (2) Is custom differentiation a real unique selling point (not "nice-to-have")? (3) Does your team have the maintenance maturity for 5 years? If 2 + 3 = yes and 1 = no, then building makes sense. Otherwise: SaaS + custom integrations.
How long does an MVP take?
For a focused self-service portal with 5–10 screens: 8–14 weeks. For more complex platforms with user roles, a custom schema and third-party integrations: 4–6 months. I spread this across 2-week sprints with a demo at the end of each sprint.
What does a custom build typically cost?
Self-service portal with standard auth + Stripe + 5–10 screens: €30–60k. Custom CRM-light or B2B marketplace: €80–150k. For significantly higher requirements (multi-tenant, complex schema): €150–300k. We clarify the precise estimate in the audit.
Do I own the code afterwards?
Yes, as standard. Repo in your GitHub account, deployment on your Vercel/hosting. I keep no licence hold, no tool lock-in. If you build the team internally, you can carry on yourself at any time — that's why I deliver docs and walkthroughs.
What does team handover look like in practice?
Architecture diagrams + code docs + 5–10 Loom walkthroughs through critical modules + 2–3 hands-on pair sessions with your lead dev. Optional: 2–3 months of support via Slack/email for questions. After that I don't disappear — I stay reachable for special topics.
Let's talk
Three paths — depending on where you are.