Neo Vision

12%

Skip to main content
/Solution Design

DESIGN

Decide how the software should work before anyone builds it. You leave with a scope a team can build and price.

A 1 to 3 week sprint that turns a chosen business problem into a defined solution: workflows, user roles and permissions, data and integration requirements, a clickable prototype, a prioritized backlog and an indicative build estimate. A product designer leads it, and a senior engineer reviews each flow against what can be built. You keep every file, whoever builds the product.

€2K

Starting at

1 to 3 weeks

Timeline

Prototype + backlog

Output

Yours

Ownership

Book a scoping call

A solution design sprint fits when…

You know the business problem, and nobody has yet defined how the product should work
Vendor estimates for the same idea differ widely, because each vendor guessed a different scope
Several stakeholders want different things from one system, and someone has to decide the flows
You want to test one AI workflow on your own data before you commit a build budget

Scope problems cost the most when developers find them mid-build.

Quotes you cannot compare

Each vendor fills the gaps in your brief with its own assumptions. The quotes end up describing different products.

Discovery that ends with the proposal

Presales workshops stop when the proposal is due. Permissions, edge cases and integrations wait until developers hit them.

Agreement that lasts until the first screens

Stakeholders agree on the idea in meetings. The disagreements appear when real screens arrive and each person sees a different product.

An AI idea tested on clean examples

The demo worked on tidy inputs. Nobody knows yet how it handles your real documents, exceptions and approval rules.

A scope your team can price

before anyone writes code.

01

The problem on one page

We write down who uses the product, what each role needs to do, and where the current process breaks. Later decisions point back to that page.

02

Workflows, roles and a prototype

We map the workflow, each user role and its permissions, and the data every step needs. The designer turns the key flows into a clickable prototype so stakeholders react to real screens early.

03

Checked by a senior engineer

Each flow gets a review for data, permissions and integration limits. Anything the budget cannot support is flagged during the sprint, before it reaches a quote.

04

A backlog any team can estimate

Every item in the prioritized backlog states its acceptance criteria. The backlog is detailed enough for an engineering team to estimate without repeating the discovery.

05

An indicative build estimate

We price the build from the backlog and name what could move the number: integrations, data quality, approval paths and security review.

06

AI workflow track

For an AI workflow, we test the critical AI step on a representative sample of your real data. That step can be extraction, classification, matching, generation or decision support. We mark where a person approves and end with a build or do-not-build decision.

A sprint takes 1 to 3 weeks, depending on how many flows are in scope.

01.

Frame the problem

Days 1-2

Sessions with the process owner and the people who do the work. We agree what the product must do first.

02.

Map workflows and roles

Week 1

Workflows, user roles, permissions and the data each step needs, reviewed with you as they take shape.

03.

Prototype and check

Week 1-2

A clickable prototype of the key flows, and an engineering review of data, permissions and integrations.

04.

Scope and hand over

Week 2-3

Backlog, acceptance criteria, indicative estimate and the Figma file, walked through with your team.

Transparent pricing. Priced before we start.

Product sprint

Start here

€2K to €6K

1 to 3 weeks. Workflows, user roles and permissions, data and integration requirements, a clickable prototype, a prioritized backlog with acceptance criteria, and an indicative build estimate.

Book a scoping call

AI workflow sprint

One AI workflow

€6K

3 weeks, fixed price. A process map, a test of the critical AI step on a representative sample of your data, approval points, acceptance criteria, and a build or do-not-build decision.

Book a scoping call

Common questions.

  • A workflow map, user roles and permissions, data and integration requirements, a clickable prototype in Figma, a prioritized backlog with acceptance criteria, and an indicative build estimate.

Bring us a problem you have chosen but not yet defined.

We’ll define how the product should work and price the build from the result.

Book a scoping call

From €2K, in 1 to 3 weeks.