Sigzen Technologies (registered trademark)

SigzenDelivery— our ERPNext implementation methodology

Six stages. A quality gate after each one. No surprises at the end.

SigzenDelivery is the method Sigzen Technologies follows on every ERPNext implementation. The project moves through six stages, and each stage ends with a quality gate — it must be signed off before the next one starts. Tests are written before anything is built, a separate consultant checks the work, and every approval is in writing.

Talk to a consultant
  • 6 stages, each closed by a quality gate
  • Independent quality assurance
  • 4 separate environments
  • One Business Analyst as your contact
The SigzenDelivery planQuality gateData migrationTraining
  1. 01

    Requirements & baseline

    Gate: Signed Business Requirement Document (BRD)

    Data migration: Data scope confirmed — standard unless agreed otherwise

  2. 02

    Solution design & test planning

    Gate: Functional design with acceptance criteria

    Data migration: Templates and field mapping

  3. 03

    Development & build

    Gate: Working solution, checked against the design

  4. 04

    Quality assurance

    Gate: Quality-assured, stable solution

  5. 05

    User acceptance testing (UAT)

    Gate: Joint UAT sign-off

    Data migration: Trial load, checked by your team

    Training: Key-user training / demo for UAT

  6. 06

    Go-live & release

    Gate: Live system + release note

    Data migration: Final load + opening balances reconciled

    Training: End-user training + user manuals

What makes SigzenDelivery different?

Quality is built in at every step, not checked only at the end.

  • Quality gates at every stage

    No stage begins until the previous one is complete and signed off. Problems are caught early, not at the finish line.

  • Tests designed before building

    Every requirement gets pass/fail acceptance criteria and test cases before development starts.

  • Independent quality assurance

    A consultant who did not build the solution tests it, and your core business flows are re-tested every cycle.

  • Written record at every hand-off

    Requirements, designs, test results, approvals and releases are documented. You always know what was agreed and delivered.

What are the stages of an ERPNext implementation at Sigzen?

Six stages: requirements, design and test planning, build, independent QA, user acceptance testing, and go-live. Each stage has an owner, a clear output and a sign-off. Data migration and training run alongside, so your data and your people are ready on go-live day.

  1. Requirements & baseline

    We document your requirements with your department champions in a Business Requirement Document (BRD). Each requirement is checked against the signed Scope of Work, and nothing is built before you approve the BRD.

    You receive
    Signed Business Requirement Document (BRD)
    Data
    Data scope confirmed — standard unless agreed otherwise
  2. Solution design & test planning

    Each requirement becomes a functional design with plain pass/fail acceptance criteria. Test cases are written now, before any development starts.

    You receive
    Functional design with acceptance criteria
    Data
    Templates and field mapping
  3. Development & build

    Our consultants build strictly against the approved design, on a separate development environment, and verify every acceptance criterion with evidence.

    You receive
    Working solution, checked against the design
  4. Quality assurance

    A consultant who did not build the solution runs every test case. Core flows — sales, purchase, stock and accounting — are re-tested. The gate passes only with zero open critical or high-priority issues.

    You receive
    Quality-assured, stable solution
  5. User acceptance testing (UAT)

    Your team validates the solution in a managed, time-boxed window — typically five working days — using a scenario pack taken from your signed BRD.

    You receive
    Joint UAT sign-off
    Data
    Trial load, checked by your team
    Training
    Key-user training / demo for UAT
  6. Go-live & release

    We deploy through a controlled release checklist and run a joint smoke test of your most critical flows. You receive a release note listing everything delivered.

    You receive
    Live system + release note
    Data
    Final load + opening balances reconciled
    Training
    End-user training + user manuals

How does Sigzen handle data migration?

Our standard scope moves the data you need to start working on day one: master data, opening balances and open transactions. Old historical transactions are not part of the standard scope — they are available as a separate, quoted scope.

  1. 1

    Confirm the scope. The standard scope applies by default. Anything extra, such as historical data, is quoted separately and recorded in the BRD.

  2. 2

    Prepare. We share import templates and a field mapping.

  3. 3

    Trial load. Data is loaded into the acceptance environment and checked by your team during UAT.

  4. 4

    Final load. At go-live we do the final load and reconcile opening balances with you.

How is training done?

Training happens in two rounds. Key users get a demonstration and training at the start of UAT, so they can test with confidence. All end users are trained before go-live, and every training is followed by user manuals.

  1. 1

    At the start of UAT. Key-user demonstration and training, so your team can test with confidence.

  2. 2

    Before go-live. End-user training for everyone who will use the system.

  3. 3

    After each training. User manuals for your team.

How do you test before go-live?

Test cases are written in Stage 2, before any build. In Stage 4 a consultant who did not build the solution runs every test and logs every result. Your core flows — sales, purchase, stock and accounting — are re-tested each cycle so nothing that works is broken.

Stage 4 · QA sign-off

Tested by an independent consultant

  • All test cases executed and logged
  • Core flows re-tested: sales, purchase, stock, accounting
  • Previously delivered features re-checked
  • Zero open critical or high-priority issues

Which environments do you use?

Four separate environments. Work moves one way only — so testing never disturbs your live system, and nothing reaches production without passing every gate.

  1. Development

    Where we build and first check the solution.

  2. Quality assurance

    Independent testing, including core-flow regression.

  3. User acceptance

    Your team validates on near-live data.

  4. Production

    Your live system — reached only through a release checklist.

Changes move in one direction only — never straight into production.

How do you handle scope and change requests?

Scope is checked against two signed documents: the Scope of Work (SOW), signed during sales, which defines what your price covers; and the BRD, signed in Stage 1, where each requirement is openly marked as in scope or as a change. Every UAT finding then goes into one of three groups. We agree this rule with you at UAT kickoff — before any findings arrive — so there are no scope disputes at invoice time.

  • Defect

    Fixed free, in the current cycle.

    Not as agreed in the BRD — The solution does not match what was signed.

  • Change request

    Quoted first, done after your approval.

    New requirement — A requirement not covered by the signed BRD.

  • Configuration / data item

    Logged with a recommended fix.

    Setup or master data item — Comes from user setup or master data, not from the build.

Who will I work with?

One dedicated Sigzen Business Analyst is your main contact from requirements to sign-off. Behind them, every activity has a named owner. Progress is shared at an agreed cadence, and the BRD, UAT and release are approved in writing.

You

Business Analyst

Owns your requirements, UAT and sign-offs. Your single point of contact.

  • Developers & consultants

    Build strictly against the approved design.

  • Independent QA consultant

    Tests what others built — a real second pair of eyes.

  • Deployment team

    Runs the release checklist and the joint smoke test at go-live.

What happens after go-live?

We stay with you. First a stabilisation period, then ongoing support through an annual maintenance plan, with new needs handled through the same clear change process.

  1. Stabilisation

    We stay close to your team to settle early questions quickly.

  2. Support & AMC

    A reliable support channel to keep your system healthy.

    ERPNext support plans
  3. Enhancements

    New requirements scoped, agreed and delivered with the same quality gates.

  4. Guidance

    Advice on getting more from ERPNext as your business grows.

Questions about SigzenDelivery

Something not covered here? Ask a consultant.

How long does user acceptance testing (UAT) take?

UAT is a managed, time-boxed window — typically five working days. It starts with a kickoff and a scenario pack taken from your signed BRD, and ends with a joint sign-off.

Do you migrate our old historical data?

Our standard scope covers master data, opening balances and open transactions — what you need to work from day one. Migrating older historical transactions is available as a separate, quoted scope.

Is training included?

Yes. Key users get a demonstration and training at the start of UAT, and all end users are trained before go-live. Each training is followed by user manuals.

What if we find something missing during UAT?

We classify it with you. If it does not match the signed BRD, it is a defect and we fix it free in the current cycle. If it is a new requirement, it is a change request — quoted first and done only after your approval.

Do you work on fixed price or hourly?

Both. Fixed-price projects are governed by the signed Scope of Work; hourly engagements are tracked through timesheets. We can advise which suits your project.

Who signs off each stage?

Your team approves the BRD, the UAT and the release in writing. Sigzen's Business Analyst coordinates every sign-off, so there is always a written record.

See SigzenDelivery applied to your project

We will walk your team through the method, share relevant case experience, and shape the plan around your business.

Talk to a consultant