Services

Business platforms & B2B marketplaces

Platforms connecting two professional populations: verified accounts, gated access, internal messaging and confidentiality by default.

Next.js
PostgreSQL
Accès par rôle

3
Work cited: 3
Technologies used: 4
Markets served: 3
Languages by default

Connecting people without exposing them

A B2B marketplace is not a directory. Its core is managing who sees what: a seller wants to be found without being identified, a buyer wants to filter before revealing themselves. We have built five platforms on that principle, across insurance broking, accountancy firms, real estate and financial recruitment.

What a delivered platform contains

Separate accounts per population, with manual or automated verification

Progressive visibility: anonymised listing, then unlocking on agreement

Internal messaging, so conversations stay on the platform

Recurring subscriptions and automated invoicing

Moderation back office: account and listing approval

Access log, to trace who viewed which document

Why code rather than an off-the-shelf product

Generic marketplace products impose their data model. Yet the business model is exactly what makes a specialised platform valuable: the confidentiality rules around selling an insurance portfolio have nothing in common with those of a shop. Everything is written bespoke, in TypeScript.

Timeline and budget

Allow three to five months for a first usable version, and a budget from €35,000. Scope is quoted feature by feature before we start.

Who this is for, and who it is not for

It is for you if two professional populations need to find each other without revealing themselves, if you charge for access rather than the transaction, and if you know a trade in detail that generic tools ignore.

It is not for you if you are after a consumer marketplace, where volume and logistics matter more than confidentiality. Other approaches suit that better, and we will tell you so rather than sell you a badly calibrated project.

The problem we will help you anticipate

An empty marketplace serves nobody: buyers do not come if there is nothing to see, sellers do not list if there is nobody there. That is a commercial problem, not a technical one, but it has direct consequences for what we build — presentable empty states, the ability to seed one side by hand, named invitations. We raise it at scoping, because ignoring it is the leading cause of failure for these products.

The screens where success is decided

On a platform, value is not decided on the homepage but on four screens: the sign-up form, the anonymised listing, the moment of unlocking, and the payment page. That is where most of the design time goes. Make the sign-up journey too long for a professional audience and the product never starts.

What is included

Scoping workshop and scope quoted line by line

Design of every screen in Figma, signed off before development

Build of the platform and its moderation back office

Subscriptions, automated invoicing and failed-payment recovery

Document access log, which may be required in a dispute

Structured data and technical SEO on the public pages

Preview environment continuously available from the first week

Handover training and written documentation

One month of warranty after launch

What is not included

Writing your business content, your terms and the legal validation of your model, acquiring the first users, and Stripe and hosting fees, which stay in your name. We give our opinion when asked, but those decisions are yours.

How we work

A preview link is opened to you in the first week: you watch the product take shape continuously, not at milestone meetings. We ship in usable increments, so a complete journey can be tested early rather than a whole product late. You talk directly to the people designing and building it — not to a project manager in between.

Hosting and data

Hosting in the European Union by default, under a processing agreement that names locations and sub-processors. For regulated professions, Swiss hosting is available. That choice is made at quotation stage, not in a conversation after launch.

Proof