Nannow: 6,000+ registrations within four months of launch

The problem: trust, payments and mobile had to work together

A two-sided marketplace cannot be only a listing directory. Different participants, their trust status, payment flow and actions in the mobile product all had to be managed.

If those parts operate separately, the transaction becomes ambiguous: users do not know who may act, when money moves or which state is final.

Constraints: two sides and one coherent transaction

The platform had to support different roles, KYC checks and Stripe Connect payment infrastructure. Those elements had to align with the mobile applications rather than remain isolated integrations.

Transaction integrity was the central architecture constraint: every role and state needed an explicit place in the overall process.

Decisions and implementation

The co-founders and team built the marketplace core, participant roles, KYC, Stripe Connect and mobile applications. These elements were designed as a single product flow.

This structure connects business rules to explicit transaction states, permissions and payment actions.

• Marketplace core
• Participant roles and permissions
• KYC
• Stripe Connect
• Mobile applications

My exact responsibility

I was Nannow's co-founder, CEO and product lead. I shaped product and business decisions and coordinated the technical implementation of the marketplace core, roles, KYC, Stripe Connect and mobile applications.

The platform was built with the other co-founders and the team, so its technical implementation and overall outcome are not presented as one person's work.

Reported outcome: more than 6,000 registrations

Within four months of launch, Nannow recorded more than 6,000 registrations.

The result records sign-ups on the launched platform. It is a registration metric—not an active-user, order, transaction or revenue metric—and is presented precisely as such.

What other products can take from this

Marketplace architecture should begin with transaction states, roles and movement of money. The interface should reflect that model rather than conceal undefined business rules.

KYC and payments are not late-stage integrations. They change the user journey, access rights and failure cases, so they belong in the product core from the start.