et

What stage is your fintech project really at?

Nine questions, and an honest answer about where you are.

Most fintech projects do not fail on the code. They fail because a decision was taken in the wrong order — architecture before jurisdiction, a vendor before a written scope, a build before anyone established whether a licence was needed. Each of those is cheap to fix in the week it happens and expensive to fix a year later.

This check asks what has actually been settled, and reports the stage that follows from your answers, the things standing between you and the next one, and the three to five actions worth taking now. It also says what you should not be paying for yet.

Who this is for

It is for the period before there is anything to audit — when the expensive decisions are still ahead of you.

  • a founder planning an investment, lending, crowdfunding or private-market platform
  • a team that has an idea and a budget and no agreed order of work
  • anyone about to commission development and unsure whether the groundwork is done
  • a company deciding whether to buy a platform now or prepare for six months first

It is not for a product that already exists and is running. That is a different set of questions, and the Technology Control Check asks them. Technology Control Check

What is asked

Nine questions drawn from the FinMV assessment — the same questions, a shorter list. Every point is traceable to an answer you gave, and a dimension nothing asked about is reported as unassessed rather than as zero.

01

Jurisdiction and regulation

Where this operates and what that implies. Jurisdiction determines the licence, the KYC obligations, the custody arrangement and a large share of the data model.

02

The model

Equity, debt, real estate, P2P or a private portal, and whether it is open to the public or invitation only. These are different products, not variations of one.

03

Licensing status

Held, applied for, still being researched, or not needed. Building on an assumed answer is how projects lose a year.

04

Scope definition

Whether what you want built is written down. Without it nobody can price the work honestly or compare two vendors fairly.

05

Technical leadership

Who inside the company can judge a technical proposal, and what happens when nobody can.

06

Budget and the decision in front of you

Whether the money to finish exists, and what you are actually trying to decide this month.

Where this stands today

The check is not open for self-service yet. What it describes is not a plan — the same questions and the same roadmap run today inside FinMV Workspace, on a project. What is missing is the door: a way to answer them without an account first.

Ask about a project

What it cannot do

  • It is not legal or regulatory advice. It can tell you which questions need a qualified answer; it cannot answer them.
  • It does not price your project. A number produced from nine multiple-choice answers would be a guess wearing a suit.
  • It reads what you tell it. Nothing here is verified against anything, and a check answered optimistically produces an optimistic result.
  • Nine questions are not an assessment. The full one asks considerably more, and this is deliberately the short version.
  • A stage is a suggestion, not a verdict. You know things this form did not ask about.