vi

Problems & Tools

Start from the decision you are facing, not from a product catalogue.

Most expensive technology mistakes are not made by people who chose badly. They are made by people who never saw the question. Each situation below is one of those questions, with what to check, what it will cost you to get wrong, and where to go next.

Buying software, choosing a vendor

You have a proposal in front of you, or three of them, and no reliable way to tell what is missing from any of them.

01

I received a software development proposal

Find what the proposal does not say. Scope that reads complete but is not, ownership left undefined, infrastructure that quietly stays with the vendor, support that turns out to be a separate contract.

Not open yet The page explains what this checks. The tool itself is not open yet.

02

I need to compare two or three vendors

Three proposals written to three different briefs cannot be compared by reading them in sequence. They have to answer the same list of questions first, and then the silences line up.

In Workspace This works inside FinMV Workspace, on a project, and needs an account.

Building a complex financial product

You are planning or mid-way through something where payments, investor money, personal data or a regulator change what "finished" means.

01

I am planning a fintech product

Where the project actually stands, what is blocking it, what has to be decided before development starts, and what not to spend money on yet.

In Workspace This works inside FinMV Workspace, on a project, and needs an account.

02

I need to prepare for launch

What is genuinely left before this can carry real users and real money — operations, evidence, and the things that are always found in the last week.

In Workspace This works inside FinMV Workspace, on a project, and needs an account.

Technology control and vendor dependency

The product works. The question is what happens to it if the people who built it stop answering.

01

Who actually controls our technology?

Repository, cloud accounts, domain and DNS, root access, database and exports, backups, third-party accounts, documentation, and how much of it depends on one person.

Coming next Decided and specified. Not built yet, and we do not promise a date.

Build, buy, or hire

Before anybody writes code, the question is whether anybody should.

01

SaaS, custom, or our own team?

An honest answer includes "buy the standard product and do not build this". Custom software is expensive to own, not only to write.

Coming next Decided and specified. Not built yet, and we do not promise a date.

Where all of this ends up

Each of these produces something worth keeping: a proposal with its gaps named, a list of questions for a vendor, a decision and the reason for it. FinMV Workspace is where that becomes a project record instead of a document you lose.