Direct naar hoofdinhoud
BuildCalcSoftware Solutions
How we work

From challenge to working solution.

Our approach is structured, transparent and value-driven. Per phase you know exactly which steps we take, what you receive and what effort we ask of your organisation.

  1. 01Discovery
  2. 02Process analysis
  3. 03Solution design
  4. 04Development
  5. 05Integration & rollout
  6. 06Support & evolution
01

Discovery

Lead time: 1–2 weeks

Establish whether there is a concrete, solvable challenge and whether we are the right partner.

Concrete steps

  1. 1Intro conversation about organisation, goals and bottlenecks
  2. 2Inventory of current systems, volumes and roles involved
  3. 3First view on direction, order of magnitude and risks
  4. 4Feasibility check on data, system access and team availability

What you receive

  • Short discovery note with the challenge and possible directions
  • Indicative investment and lead time (range)
  • Proposal for the next step

Your effort: One 60-minute conversation with the key roles.

02

Process analysis

Lead time: 2–3 weeks

Understand the process, system landscape and data flows before anything is built.

Concrete steps

  1. 1Working sessions per role covering exceptions, not just the happy path
  2. 2Mapping systems, integrations and shadow IT
  3. 3Defining ownership per data object
  4. 4Bottleneck analysis with estimated impact
  5. 5Prioritisation on value versus feasibility

What you receive

  • Process map of current and target situation
  • System and data landscape with master-data agreements
  • Quantified bottleneck analysis
  • Twelve-month roadmap

Your effort: Three to five 90-minute sessions and sample documents.

03

Solution design

Lead time: 2–4 weeks

A design that users and administrators recognise, with a fixed scope.

Concrete steps

  1. 1Functional design: user journeys, screens and business rules
  2. 2Technical design: data model, architecture, interfaces and hosting
  3. 3Clickable prototype of the core screens
  4. 4Security, roles, permissions and GDPR principles
  5. 5Scope definition for phase one

What you receive

  • Functional and technical design
  • Clickable prototype
  • Fixed or capped estimate
  • Schedule with demo dates

Your effort: Prototype review and scope sign-off.

04

Development

Lead time: 6–16 weeks depending on scope

Deliver working software in short iterations that you can judge yourself.

Concrete steps

  1. 1Two-week sprints with a demo at the end of each
  2. 2Automated testing of business rules and calculation logic
  3. 3Interim delivery to a test environment
  4. 4Weekly progress report on scope, schedule and budget
  5. 5Feedback handled in a transparent backlog

What you receive

  • Working software after each sprint
  • Test report and open items
  • Up-to-date backlog
  • Source code in a repository you own

Your effort: One decision-maker and about two hours per sprint.

05

Integration & rollout

Lead time: 2–6 weeks

Make the solution work inside your landscape and your organisation.

Concrete steps

  1. 1Building and testing integrations with existing systems
  2. 2Data migration including cleaning and duplicate checks
  3. 3Acceptance testing with real users and real data
  4. 4Role-based instruction and short work instructions
  5. 5Phased go-live, in parallel with the old way of working where needed

What you receive

  • Working integrations with monitoring
  • Migration report with control totals
  • Signed acceptance test report
  • User and admin documentation

Your effort: Availability of key users for acceptance testing.

06

Support & evolution

Lead time: Ongoing

Keep the solution reliable and let it grow with your organisation.

Concrete steps

  1. 1Monitoring of integrations, performance and errors
  2. 2Support with agreed response times
  3. 3Periodic maintenance: updates, security and dependencies
  4. 4Quarterly review on new needs and roadmap

What you receive

  • Service agreement with response times
  • Monthly availability and incident report
  • Prioritised development backlog

Your effort: One quarterly review and a contact for prioritisation.

Principles

What we stand by.

  • Transparent communication with one point of contact
  • Iterative development with working increments
  • Periodic demos instead of surprises at delivery
  • Clear scope with explicit exclusions
  • User adoption focus from day one
  • Documentation of business rules, integrations and support
  • Source code and data owned by the client
  • Support and evolution after delivery
Roles and governance

Who does what during an engagement.

Most digitalisation projects fail on unclear roles and slow decisions, not on technology. That is why we make those roles explicit at the start.

Your project owner
One person with a mandate to decide on scope, priority and budget. Without that mandate projects stall on decision-making, not on technology.
Key users
Two or three people who do the work daily. They review designs, run acceptance testing and later champion the solution internally.
Our lead engineer
Responsible for architecture, quality and technical choices throughout — the same person from design to operations.
Your IT partner or admin
Involved in access, security, hosting and releases. We align actively instead of working around them.
Phase-based decisions
Each phase ends with a go/no-go based on results and measurement. Continuing is a deliberate choice, not a default.
Escalation and adjustment
If something slips or scope changes, we raise it within the current cycle with options and consequences — not afterwards.
Deliverables and rhythm

What each phase concretely produces.

Alongside working software, every engagement produces documentation, measurements and support agreements — making the result transferable and verifiable, even years later.

Documents you receive

Every phase produces documentation that stands on its own and remains useful after the engagement.

  • Process map and bottleneck analysis
  • Functional and technical design
  • Test report and acceptance record
  • Operations pack and handover document

Rhythm and meetings

A fixed, lightweight meeting rhythm that gives control without filling your calendar.

  • Weekly thirty-minute progress check
  • Demo of working software every two weeks
  • Monthly steering report on scope, budget and risk
  • Quarterly roadmap during operations

Quality assurance

Quality is built into the process rather than depending on a final inspection.

  • Automated tests on critical logic
  • Code review on every change
  • Security and access review before go-live
  • Monitoring and logging from day one

Measuring effect

We define up front what the result is measured against, keeping the business case testable.

  • Baseline at the start
  • Measurement at delivery
  • Evaluation after three months of use
  • Roadmap adjustment based on the numbers
Questions

Frequently asked questions about our approach.

The questions clients ask us most before a project starts.

See project examples Read our knowledge base See our services
Get started

Which processes could run smarter in your organisation?

In a no-obligation intro call we discuss where automation, integration or custom software adds value right away.

Get in touch →