NDA before system access
EN

Language

Start a project
Start a project

How we work

Clear scope, fewer meetings and progress you can see.

From the first conversation, you know what we need from you, what happens on our side and what makes a stage complete. We adapt the entry to the situation: taking over an existing system, building a B2B tool or supporting a software house under NDA.

Start a project

Working principles

The process should reduce your workload, not add another calendar full of meetings.

We need one decision-maker, access to the right context and answers at agreed points. The rest runs asynchronously, with a clear written status and scheduled checkpoints.

Scope the first stage first
We do not try to price an entire legacy system from a short description. We separate confirmed work from unknowns and estimate what has clear boundaries.
Decisions without daily meetings
Progress, risks and questions are recorded asynchronously. We meet when a decision is needed or there is working software to review.
Code and knowledge remain accessible
We organise repositories, accounts, environments and documentation in the agreed model so the client or nominated partner retains access.

From first contact to ongoing support

Seven stages. Each ends with a concrete output.

For a straightforward project, some stages can happen together. None exists to create workshops for their own sake.

  1. Do I need a finished specification?

    Initial fit check

    We start with a short description of the problem, system, timing and business impact—not a form full of technical answers.

    What we need from you

    • You send the situation, expected outcome and what is currently blocking the work.
    • You identify the person who can decide on the next step.

    What CODEVENOM does

    • We check whether the problem fits our services and current availability.
    • We tell you what information is needed for the first conversation or initial assessment.

    What you have after this stageA decision on whether to continue and what should happen next.

  2. Do you need full access from the start?

    Context and controlled access

    We ask only for the people, material and environments needed to assess the agreed area.

    What we need from you

    • You provide access to the relevant people, material and systems needed for the assessment.
    • You explain business and security constraints, deadlines and critical integrations.

    What CODEVENOM does

    • We review the available code, documentation, environments and current way of working.
    • We connect the technical picture with the process, users and business impact.

    What you have after this stageA shared view of the system, its dependencies and the most important unknowns.

  3. When will I receive scope and an estimate?

    First-stage scope

    We separate confirmed work from unknowns so the estimate has clear boundaries and assumptions.

    What we need from you

    • You confirm the priority, expected outcome and available budget cap.
    • You make decisions where the choice depends on the process or business outcome.

    What CODEVENOM does

    • We describe scope, assumptions, exclusions, dependencies and acceptance criteria.
    • We propose T&M or fixed price and estimate the time and cost of the first stage.

    What you have after this stageA proposal covering the scope, boundaries, commercial model and terms of the first stage.

  4. What must be agreed before work starts?

    Agreement and preparation

    Before work begins, we agree the documents, payment, access, communication and acceptance process.

    What we need from you

    • You agree the relevant documents—NDA, MSA and SOW or order—depending on the engagement.
    • You make the upfront payment if the proposal requires one and provide the agreed access.

    What CODEVENOM does

    • We prepare or agree the documents, schedule, payment terms and acceptance process.
    • We establish the communication channel, working environment, status rhythm and demo or review dates.

    What you have after this stageAgreed commercial terms, a confirmed start date and operational readiness.

  5. How many meetings will the project require?

    Delivery and regular demos

    We work mainly asynchronously. Written status stays available throughout, while demos or reviews follow an agreed rhythm—usually every one or two weeks.

    What we need from you

    • One decision-maker answers questions and approves changes within the agreed time.
    • You join the scheduled demo or review and provide feedback.

    What CODEVENOM does

    • We deliver the agreed scope and show progress, risk, budget use and decisions needed.
    • We demonstrate working increments and ask for approval before changing direction or scope.

    What you have after this stageVisible progress without daily status meetings or silent scope expansion.

  6. How do we know when a stage is complete?

    Acceptance and release

    We compare the result with the agreed scope and acceptance criteria. A code handover alone does not close the stage.

    What we need from you

    • You verify the result against the process and user needs within the agreed review period.
    • You confirm release, handover or the start of the next stage.

    What CODEVENOM does

    • We prepare the demo, technical checks, release material and documentation appropriate to the scope.
    • We resolve agreed discrepancies within scope or show their effect on further work.

    What you have after this stageAn accepted release, a list of known constraints and an agreed next action.

  7. Am I tied to CODEVENOM after launch?

    Maintenance, further development or handover

    No. After acceptance, you can ask us to maintain or extend the system, or hand it to your own team or another partner.

    What we need from you

    • You choose the future working model, priorities and budget for the next period.
    • You share information from production use and changing needs.

    What CODEVENOM does

    • We agree maintenance scope, reporting route and response times separately.
    • We can continue development or prepare a handover of code, access and knowledge.

    What you have after this stageA system prepared for the agreed support model or handover, with clear access and next tasks.

Commercial model

T&M for unknowns. Fixed price for contained scope.

The proposal or SOW sets out the commercial model, budget cap, payment terms and acceptance process. Exceeding the cap or changing scope requires the client’s prior approval.

T&M for takeovers and legacy work

When scope cannot be contained credibly before entering the system, we bill actual work up to the agreed cap and report budget use regularly.

Fixed price for a well-contained scope

A fixed price works when the outcome, dependencies, exclusions and acceptance criteria are clear enough before work begins.

Start with a short description

Show us the system or process holding the business back.

Tell us what is not working, what outcome you need and by when. We will assess the fit and tell you what we need to scope the first stage.

Start a project
How we work — CODEVENOM delivery process