Lead times and implementation

From module selection to a working WebApp.

First the right data, then the chosen functions. See how we assess your sources, normalise data, connect APIs and use Trello to work towards a controlled handover.

Your choice determines the setup

These modules are included in your roadmap.

The configurator automatically passes on your chosen modules and required dependencies. Make changes in the module selector; this page follows your selection.

  • Sales reporting
  • Inventory
  • Orders
View preparation for each module

Sales reporting

Align sales channels, revenue, VAT, purchasing costs and margin and compare with the source.

Inventory

Check SKUs, EANs, locations and available stock; explain differences between sources.

Orders

Check order lines, statuses, amounts and delivery details. Returns processing remains separate custom work.

The estimate takes your chosen modules into account. The number of sources, data quality, API access, new integrations and feedback determine the final schedule. We agree that schedule after the initial assessment.

A clear route to handover

Eight phases with a clear outcome at every step.

This is the broad sequence. Data work, API connections and module design can partly run in parallel. We adapt the actual schedule to your situation.

  1. Assessment and scope

    Translate your module selection into required sources, users and a clear first release.

    Learn more

    We assess available data, history, volumes, API access and who reviews the data. We also record the leading source and what falls outside the brief.

    Ready for the next step: An agreed scope, source list and acceptance criteria.

  2. Load available data

    Load the first available data into the agreed environment.

    Learn more

    We check files or source data for completeness and provenance. A temporary Excel or CSV import can support an initial trial; automatic processing is set up for daily use.

    Ready for the next step: A verifiable initial dataset with known gaps.

  3. Normalise data

    Make different sources comparable and prevent double counting.

    Learn more

    Product codes, EANs, dates, VAT, currencies and statuses get an agreed meaning. We link records and compare quantities and totals with the source.

    Ready for the next step: A consistent data foundation with explained differences.

  4. Connect and update APIs

    Set up the agreed integrations and automatic updates.

    Learn more

    We test access, data flows, synchronisation intervals and error messages. We make processing times visible. New API integrations receive their own scope and estimate in advance.

    Ready for the next step: Working data flows with checks on freshness and errors.

  5. Design and configure your modules

    Configure only the chosen modules and required components for your workflow.

    Learn more

    Existing functions form the foundation. Together, we define screens, filters, roles and approvals. Additional design or development is agreed separately.

    Ready for the next step: A usable first version of the agreed module workflows.

  6. Test and adjust through Trello

    Walk through real tasks and turn findings into concrete actions.

    Learn more

    For example, you check an order, stock discrepancy or pick list. Feedback and issues go onto the project board with an owner and acceptance criterion. After adjustments, we test again.

    Ready for the next step: Verified scenarios and resolved findings within the scope.

  7. Acceptance and launch

    Review the final version together and agree the launch date.

    Learn more

    We check the agreed functions, data, access and open items. We launch only after the agreed approval; remaining extensions get their own follow-up schedule.

    Ready for the next step: Approval of the agreed delivery and a clear launch date.

  8. Handover and aftercare

    Get guidance on usage and arrangements for management and support.

    Learn more

    We hand over the workflow and contact arrangements and follow the initial processing as agreed. Hosting, backups, monitoring and regular maintenance are part of the package; new functions are discussed separately.

    Ready for the next step: A handed-over workspace and arrangements for management and next steps.

From feedback to an agreed action

Trello keeps progress and adjustments clear.

For each task, we record its module, intended outcome, owner and approval criterion. You can see which information is missing and which items are ready to test.

Sample screen 1 · Project boardSample project tasks
Trello
Project overviewSample board

To do 2

Planning

Define wishes and goals

☰   2/4
Information

Collect the required information

☰   1

In progress 2

In progress

Develop the first version

☰   3/5
In progress

Build agreed components

☰   1

For review 2

Feedback

Review the first version

☰   2
Feedback

Discuss outstanding items

☰   1

Completed 2

Approved

Goals agreed

✓
Approved

Schedule confirmed

✓
An example workflow: each card has an owner, a status and a next step.
Sample screen 2 · Task detailsSample project task
FeedbackFor review

Review the first version

Review the first version and collect feedback for the next step.

Part First versionStatus For review
Checklist2 of 3 complete
  • Check the agreed items
  • Collect comments
  • Discuss the next step
The task details keep agreements, checks and feedback in one place.

Want to follow your project and leave feedback? Create a free Trello account now. You will receive access to the project board once we start working together.

Create a Trello account ↗

Feedback gets a clear place

An unclear figure or missing action becomes a concrete card with a verifiable outcome. We discuss its priority and test the adjustment again.

New requests are assessed first

Does a request fall outside the agreed brief? We make its impact on scope, cost and lead time clear. That extension is carried out only after approval.

Ready means: checked, agreed and handed over.

We work towards a final phase with clear agreements, so you know when your WebApp can be used.

Data agrees with the source

Quantities, amounts and statuses have been compared; known differences and limitations are explained.

Your daily work has been tested

The agreed module workflows and roles have been tested and delivery items reviewed together.

You know how to move forward

Usage, management, support and possible next steps are discussed and documented.

Questions about starting and handover.

Is the displayed lead time a fixed delivery date?

No. This is an illustrative estimate for existing modules based on your selection. After assessing sources, access and extra requirements, we agree a realistic schedule and delivery milestones.

What if data or API access is still missing?

The missing item becomes a task in Trello. It may block the start or a later phase. We agree who supplies it and adjust the schedule to actual availability.

Can we start with an Excel or CSV file?

A temporary import can help explore available data and test a first version. For daily use, we retrieve the agreed data through APIs. New integrations or data cleanup are discussed in advance.

What happens if new requests arise during testing?

We distinguish a finding within the agreed functionality from a new extension. Both go on the project board, but extra work first gets its own scope, price and schedule.

Does everything have to launch at once?

Not always. We can agree a useful first release and expand later. Required dependencies, data quality and relationships between modules determine what can responsibly launch together.

Our approach

What you can expect from OptiCore.