Sales reporting
Align sales channels, revenue, VAT, purchasing costs and margin and compare with the source.
Lead times and implementation
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
The configurator automatically passes on your chosen modules and required dependencies. Make changes in the module selector; this page follows your selection.
Align sales channels, revenue, VAT, purchasing costs and margin and compare with the source.
Check SKUs, EANs, locations and available stock; explain differences between sources.
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
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.
Translate your module selection into required sources, users and a clear first release.
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.
Load the first available data into the agreed environment.
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.
Make different sources comparable and prevent double counting.
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.
Set up the agreed integrations and automatic updates.
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.
Configure only the chosen modules and required components for your workflow.
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.
Walk through real tasks and turn findings into concrete actions.
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.
Review the final version together and agree the launch date.
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.
Get guidance on usage and arrangements for management and support.
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
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.
Define wishes and goals
☰ 2/4Collect the required information
☰ 1Develop the first version
☰ 3/5Build agreed components
☰ 1Review the first version
☰ 2Discuss outstanding items
☰ 1Goals agreed
✓Schedule confirmed
✓Review the first version and collect feedback for the next step.
The first version is ready. We will review the feedback together.
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 ↗An unclear figure or missing action becomes a concrete card with a verifiable outcome. We discuss its priority and test the adjustment again.
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.
We work towards a final phase with clear agreements, so you know when your WebApp can be used.
Quantities, amounts and statuses have been compared; known differences and limitations are explained.
The agreed module workflows and roles have been tested and delivery items reviewed together.
Usage, management, support and possible next steps are discussed and documented.
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.
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.
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.
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.
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

We make agreements easy to understand and keep you informed about progress, decisions and next steps.

We bring relevant figures together and explain what they mean, helping you decide where action is needed.

We look at which recurring steps could work smarter, with attention to checks, exceptions and the people using them.

We start with a clearly defined step. Then we expand with purpose, based on what your business and workflow need.