Our process

From discovery to launch, a clear process at every step

We run projects with enterprise discipline: written scope, a clear timeline, regular demos and support that continues after launch.

5clearly defined steps

3–5 daysto a written proposal

2 weekssprint and demo cycle

1 business dayto our first reply

Step by step

How does your project progress?

Every step ends with something concrete in your hands, and we only move on with your approval.

The fountr project team in a planning session
  1. 01

    Discovery & needs analysis

    Duration: 1 week

    In a free initial meeting we listen to your goals, current systems and priorities, and identify together which work will pay back fastest.

    What you get from this step

    • Summary of needs and goals
    • Notes on current systems and processes
    • Prioritised list of work
  2. 02

    Strategy & proposal

    Duration: 3–5 days

    We prepare a written roadmap and proposal that pins down scope, deliverables, timeline and budget. No surprise costs.

    What you get from this step

    • Scope and list of deliverables
    • Timeline and milestones
    • Written proposal and budget
  3. 03

    Design & prototype

    Duration: 1–3 weeks

    We validate the idea with screen designs, architecture and, where useful, a working prototype. Nothing moves to development without your approval.

    What you get from this step

    • Screen designs or site plans
    • Technical architecture
    • Approved prototype
  4. 04

    Build & test

    Duration: 4–12 weeks

    We build in two-week sprints and demo a working version at the end of each one. Quality, security and performance testing are built in.

    What you get from this step

    • Working releases at the end of each sprint
    • Test and quality records
    • Up-to-date project board
  5. 05

    Launch & ongoing support

    Duration: Ongoing

    We go live, train your team and keep growing results with monthly support, SEO/GEO and continuous improvement.

    What you get from this step

    • Go-live and data migration
    • User training and documentation
    • Support and improvement plan

How we adapt to each type of project

The core process stays the same; what happens in each step depends on the kind of work.

Software projects

For custom software such as OMS, CRM and warehouse & barcode systems, we work in two-week sprints.

  1. 1Process analysis and scope document
  2. 2Screen designs and prototype
  3. 3Sprint-based development and demos
  4. 4Data migration, training and go-live
Learn more

IT infrastructure and security installations

For networks, servers, CCTV and fire alarms, an on-site survey and proper system design are decisive.

  1. 1On-site survey and risk assessment
  2. 2System design and bill of materials
  3. 3Planned installation and commissioning
  4. 4Testing, documentation and periodic maintenance
Learn more

Web and digital growth

For websites, SEO/GEO and advertising, measurement after launch and a monthly improvement cycle are key.

  1. 1Goals, audience and competitor analysis
  2. 2Design, content and technical set-up
  3. 3Launch and measurement tracking
  4. 4Monthly reporting and improvement
Learn more

Our working principles

01

Everything in writing

Scope, timeline, budget and acceptance criteria are agreed in writing before we start.

02

A demo every two weeks

You see a working build at the end of each sprint and can change direction early.

03

One project manager

A single point of contact for every question; you never wonder who to call.

04

Measurable goals

Every project is tied to concrete goals such as traffic, conversions or time saved.

Common questions about our process

How long does a typical project take?

It depends on scope. Corporate websites usually take a few weeks, while custom software can take several months depending on the number of modules. After discovery we give you a written, step-by-step timeline.

How do I keep track of progress?

You get a single project manager who shares regular updates, and on software projects we review a working version together every two weeks.

What happens if the scope changes mid-project?

We put every change request in writing along with its impact on time and cost. Once you approve it, we add it to the plan — there are no extra costs without your sign-off.

What happens after launch?

We train your team and hand over documentation, then continue maintenance, updates and improvements under the support plan that suits you.

Let’s talk about your project

In a free 30-minute discovery call we’ll listen to your needs and map out the best path forward.