How we work with you

A free workshop first. Then scope you approve, cycle by cycle.

We build the application around your financial models and workflows, on top of our calculation engine, not the other way round. You keep your valuation methodology; the software adapts to it. Nothing is built before it is written down, estimated in story points and approved by you, and you test every delivery on real valuation scenarios with your own data.

repeat each cycle Discovery workshop free, up to one day Agreement contract signed here Initial requirements two tracks, fixed package Delivery cycle pick · estimate · approve · test Go-live the cycle continues

The contract is signed after the free workshop. Scope and price are not fixed up front: each cycle is estimated in story points and approved by you before work starts.

  1. 1

    Step 1Discovery workshop

    Free, up to one day. Led by your project owner, we walk through your valuation processes with your team: models, data sources, reports.

    Within a few days you receive a short write-up: a scope outline, open questions, and a first estimate in story points.

  2. 2

    Step 2Agreement

    On the basis of the write-up we sign a development agreement. It covers the initial requirements phase as a fixed package and sets the terms for the delivery cycle: story-point rate, cycle length, hosting, IP, data protection.

    Scope is not fixed up front. It is agreed cycle by cycle, in story points, as described in step 4.

  3. 3

    Step 3Initial requirements

    Two tracks run in parallel.

    Financial models

    We analyse your existing valuation models (Excel, ARGUS, EstateMaster exports) and capture the requirements for the future ones: inputs, assumptions, calculation logic, outputs, reports.

    → Model requirements, plus anything our engine does not yet do, estimated separately

    Data infrastructure

    We map where your data lives today: market assumption databases, client documents, reporting and BI tools.

    → The integrations, data flows and validation rules to build

    Both tracks end in a baseline specification and a prioritised backlog with story-point estimates. This gives you the overall budget range and the order in which things get built.

  4. 4

    Step 4Delivery cycle

    From here we work in short cycles. Each cycle:

    01

    Pick and refine

    Together with your owner we take the next items from the backlog and refine them into concrete requirements.

    02

    Estimate and approve

    We estimate each item in story points (1, 2, 3, 5 or 8). You approve the cycle's scope before any work starts.

    03

    Build and deliver

    The items land in a test environment, where you run real valuation scenarios with your own data and models, not mock-ups.

    04

    Feed back

    What you learn from testing shapes the next cycle: new items, changed priorities, dropped items.

    Only approved story points are invoiced. The baseline specification is kept current throughout, so at any point you have a documented picture of what exists, what is in progress and what remains.

  5. 5

    Step 5Go-live and beyond

    Once the backlog covers your first end-to-end valuation process, we go live: your users, your hosting choice, your data migrated.

    The delivery cycle continues for further models and features as long as you need it. From go-live the commercial model applies, and improvements to the calculation engine and core platform reach you continuously.

The working group

Every project needs a small, named group on your side. We ask you to name these people before the discovery workshop.

Required

Project owner

One person who has a stake in the outcome: they will use the application themselves and train their colleagues on it. They have the authority to give us access to the data, models and systems we need.

Leads the discovery workshop, approves the scope of every cycle, and is the first to test every delivery.

A few hours per week
Financial models

Valuation expert(s)

The people who build and run your models today. Often this is the owner; for several model types it may be two or three people.

Mostly in step 3, then as questions come up
Data infrastructure

IT / data contact

One person for database access, document sources, BI tools, hosting and security questions.

Mostly in step 3, then at integration points

Experience shows the project owner is the single biggest factor in whether a project lands. On our side you get a fixed counterpart for the whole project: one person who runs the workshops, writes the specification and reports progress.

What else we need from you

  • Your models. Excel is fine.
  • Example reports and deliverables.
  • Access to your data sources for the infrastructure review.

Start with a free discovery workshop.

Bring one of your valuation processes. Within a few days you have a scope outline and a first estimate, at no cost and with no commitment.