Western Europe B2B Marketplace
One Upwork admin-panel task became a 2-engineer dedicated team, two C-suite referrals, an in-person Vienna meeting, and a named Austria reference. The CTO asked for more capacity two weeks in.
Expansion
C-suite referrals
Extra dev requested
Where the client was stuck
The client was a pre-revenue Vienna coworking startup preparing for legal-entity launch and an investment round, with no in-house engineering capacity for the internal tools they needed next. The first Upwork brief was small and concrete: a Stripe-billed admin panel on React + Refine, backed by Supabase. The real test was whether anyone outside the founding team could be trusted with business logic without being babysat. CTOs do not expand from one task to a dedicated team unless the first task proves judgment.
What we built
Inside nine days, before any SOW existed, Gerald S, the CTO and co-founder, wrote: "good know that you have some experts. Infrastructure stuff isnt my strength." From there the engagement compounded. We embedded a dedicated team across two client-owned products: the core booking platform (Next.js, Express, Supabase, Stripe, React + Refine admin) and a second portfolio product (Fastify, Supabase, Next.js). Our engineers owned three wins that were never on the original brief. They shipped Stripe end-to-end. They proposed Sentry across web and API, which surfaced a Google Maps render loop driving budget overrun. They designed a guest-user search funnel that doubles as an acquisition channel for new office supply. Direct CTO access, weekly working calls, and engineer-authored API and frontend docs kept business logic and code in the same conversation.
How one Upwork task became a dedicated team
The cleanest way to measure an outstaffing engagement is whether the client keeps increasing trust. Here is what that looked like, month by month.
Numbers that speak for themselves
What powered this build
“Especially with Roman, he is implementing things fast and with high quality.”
Gerald S
CTO & Co-Founder