How we take a systeminto production

Business system projects almost always fail for two reasons: unwritten requirements and badly migrated data. Our method is built to keep both under control.

  1. 01

    Assessment and process analysis

    Interviews with the departments, mapping of the systems already in use, identification of the breaking points and definition of measurable project goals.

    • 1-2 weeks
    • Assessment document
  2. 02

    Functional blueprint and architecture

    Functional specifications, data model, integration architecture, migration plan and a costed estimate with contractual milestones.

    • 2-3 weeks
    • Statement of work and project plan
  3. 03

    Sprint-based development

    Incremental releases to a staging environment, demos with your key users every two weeks, progress tracked on a board shared with the client.

    • 4-16 weeks
    • Always up-to-date staging environment
  4. 04

    Data migration and acceptance

    Import, cleansing and reconciliation of historical records, acceptance testing with real users, load and response-time verification.

    • 1-3 weeks
    • Signed acceptance report
  5. 05

    Go-live and training

    Planned cutover with a rollback plan, side-by-side support for each department, operating manuals and reinforced coverage in the first weeks.

    • 1 week
    • Manuals and training sessions
  6. 06

    Support and evolution

    Support contract with SLAs, proactive monitoring, regulatory updates and new functionality planned on a shared roadmap.

    • Ongoing
    • Periodic report and roadmap

A business system typically goes live in 4 to 6 months

With the first module usable from month two: we release by functional area, so the company sees a return before the project ends.

Engagement model

Three ways to work together,all of them written down

We don't sell undifferentiated hours. We agree on the format that fits the scope of the project and put it in writing before starting.

Fixed-scope project

Defined perimeter, defined budget.

When
New system, module, integration or portal with clear requirements
Duration
4-16 weeks
Billing
On milestones and progress reports
Governance
Signed statement of work and acceptance report

Dedicated team

Continuous development capacity.

When
Ongoing evolution of a system already in production
Duration
3-12 months, renewable
Billing
Monthly fee for allocated capacity
Governance
Two-week sprints, one technical lead

Maintenance and SLA

Looking after live systems.

When
Critical platforms that must stay operational
Duration
Annual contract
Billing
Support fee plus a pool of development hours
Governance
SLA with response and restore times

Scope and budget agreed upfront

Requirements, milestones and costs are formalised in a project document. No open-ended quotes and no surprises halfway through.

One technical point of contact

A project manager follows the work end to end and is your single point of contact, with agreed periodic updates.

Delivery on verifiable milestones

Every sprint closes with a working increment you can test, not with a declared completion percentage.

Documentation and handover

Commented code, technical and functional documentation, credentials and environments: everything can be handed to an internal team at any time.

Rebuilding a business system, or stuck with systems that don't talk?

A 30-minute call is enough to tell whether the project makes sense: scope, integrations required and the order of magnitude of time and cost. No commitment.

Request an assessmentSee the case studies
  • Reply within one business day
  • First analysis call is free
  • NDA on request
Previous pageIntegrationsNext pageSecurity and continuity