Dealmood & Solutions logo
Dealmood & Solutions
Get in touch with us
How we work

How we run your SAP solutions project

From the first conversation to delivery, every decision is explained, every step produces a verifiable result and nothing moves forward without your approval.

Choose your starting pointBack to the service

Where you stand

We don't restart every project from scratch.

We tailor the first days of the engagement to your reality: a brand-new idea, an existing solution or a problem that needs solving fast.

Growing SME01

You want to move to SAP Business One

Your accounting and current tools can no longer keep up: we prepare and run your SAP Business One implementation.

How we get started

  • Analysis of your processes and volumes
  • Honest comparison with Odoo for your case
  • Project plan, licences and data migration
SAP already running02

SAP needs to talk to your other tools

We connect your SAP (Business One, ECC or S/4HANA) to your website, e-commerce, CRM or a mobile app.

How we get started

  • Inventory of data flows and manual re-keying
  • Choice of APIs: OData, Service Layer, BAPI or IDoc
  • Interface prototype on a priority flow
Heading for S/4HANA03

You are still on SAP ECC

We assess your system, custom developments and data to build a realistic S/4HANA roadmap.

How we get started

  • Inventory of custom developments
  • Choice between conversion, new implementation or selective approach
  • Data clean-up plan

The full process

A clear path forward, with no gray areas.

At every step, you know what was done, what was delivered and what decision is needed to move on.

  1. 011 to 3 weeks

    SAP landscape analysis

    We map your systems, flows and developments to decide what stays in SAP and what is built next to it.

    What we do

    • Workshops with business teams and the SAP team
    • Review of interfaces and volumes
    • Security and authorisation rules

    Why this step: In an SAP landscape, a misplaced development weighs down every update and every future migration. This analysis avoids modifying the core without good reason and stacking up fragile interfaces: you get a target architecture that is easy to maintain and a costed action plan.

    How we proceed, line by line

    1. 1 An initial video call with your SAP team or license partner helps us understand your version, modules and constraints.
    2. 2 We run video workshops with business teams to identify manual re-keying, parallel files and bottlenecks.
    3. 3 We inventory existing interfaces, their volumes and frequencies, and custom developments, in a shared spreadsheet.
    4. 4 With your team, we review the security rules, roles and authorizations that will apply to the new flows.
    5. 5 For each need, we decide what stays in SAP and what gets built alongside it, and which API to use: Service Layer, OData, BAPI, IDoc or SAP BTP.
    6. 6 We write the target architecture, the technical choices and an action plan costed by batch.
    7. 7 A debrief meeting lets us review the target with your SAP team and decide on priorities.

    Who does what

    An SAP consultant and an integration architect lead the workshops and write the target, with a project manager coordinating the discussions. On your side, the internal SAP team or your license partner and the business leads contribute their knowledge of the system.

    What you provide

    • The presence of your SAP team or license partner at the technical workshops.
    • Existing documentation: architecture diagrams, interface list, development specifications.
    • Internal security rules and authorization policy.
    • Availability of business leads to describe their processes.

    What you receive

    Target architecture, API choices and action plan

    Your approval

    You approve the target with your SAP team or licensing partner.

  2. 021 to 2 weeks

    Design and prototype

    We prove the solution on a first flow or screen before rolling it out.

    What we do

    • Fiori or mobile mock-ups
    • Connection to an SAP test environment
    • Acceptance criteria and test data

    Why this step: An SAP project can hit an API limit, a missing authorization or a misunderstood screen late in the game. Proving the solution on a first flow or a first screen removes these risks early, and lets you judge on something concrete before funding the rest.

    How we proceed, line by line

    1. 1 We choose with you the most representative flow or screen to serve as the prototype.
    2. 2 We design clickable Fiori or mobile mockups, which your users test by video call before any development.
    3. 3 Your SAP team gives us access to a test environment with a technical user that has limited rights.
    4. 4 We build the prototype connected to SAP, reading and writing real test data.
    5. 5 We write with you the acceptance criteria and test data sets that will be used for each subsequent batch.
    6. 6 We demo the prototype, then your users test it themselves and send us their feedback.

    Who does what

    A designer creates the mockups, an SAP developer builds the prototype and the SAP consultant writes the acceptance criteria. Your SAP team provides the test environment and your users test the mockups and then the prototype.

    What you provide

    • Access to an SAP test environment, with a dedicated technical user.
    • Test data representative of your real cases.
    • A few users available to test the mockups and the prototype.

    What you receive

    Working prototype connected to SAP

    Your approval

    You test the prototype on your test data.

  3. 032-week cycles

    Build and testing

    We build interfaces, apps and configuration in batches, tested end to end with your teams.

    What we do

    • Development on SAP BTP, Service Layer or OData
    • Error handling, retries and logging
    • Load testing and business acceptance

    Why this step: Delivering everything in one block makes errors hard to isolate and acceptance testing endless. By moving forward in batches tested end to end, each flow is reliable before the next one, and error cases are anticipated instead of discovered in production.

    How we proceed, line by line

    1. 1 We split the work into two-week batches, each with the acceptance criteria defined in the previous step.
    2. 2 We develop interfaces, applications and extensions on SAP BTP, Service Layer or OData, without modifying the SAP core.
    3. 3 Each flow includes logging, alerts and an error recovery mechanism.
    4. 4 The code is versioned, reviewed by a second developer and covered by automated tests.
    5. 5 We run load tests on the volumes identified during the analysis.
    6. 6 Your teams carry out business acceptance testing on the test environment and record their comments in a shared spreadsheet.
    7. 7 We deliver the technical documentation for each batch, then the batch is accepted during a video review.

    Who does what

    The SAP and integration developers deliver the batches, the SAP consultant prepares acceptance testing and the project manager tracks progress. Your SAP team checks the technical aspects and your key users approve each batch from a business perspective.

    What you provide

    • Continued access to test environments and, if needed, to the systems to connect.
    • Key users available for acceptance testing of each batch.
    • Quick answers from your SAP team on authorizations and configuration.
    • Formal acceptance of each batch against the agreed criteria.

    What you receive

    Approved batches and technical documentation

    Your approval

    Each batch is accepted against the criteria defined together.

  4. 04Go-live, then ongoing

    Go-live and follow-up

    We deploy in coordination with your SAP teams, monitor the flows and evolve the solution.

    What we do

    • Planned transport and deployment
    • Interface monitoring and alerts
    • User training and support

    Why this step: A poorly coordinated SAP go-live can block orders or invoices. A deployment planned with your teams, active monitoring and a clear runbook mean any incident is spotted quickly and handled without improvisation.

    How we proceed, line by line

    1. 1 We plan the deployment window and the order of transports with your SAP team.
    2. 2 We deploy according to this plan, then check the first live flows with your teams.
    3. 3 We activate interface monitoring and alerts sent to the right people.
    4. 4 We hand over a runbook describing, for each incident, the signs, checks and actions to take.
    5. 5 We train your users by video call and provide enhanced support during the first weeks.
    6. 6 We then evolve the solution according to your priorities, with scheduled deployments.

    Who does what

    The project manager coordinates the deployment, the developers monitor the flows and fix issues, and a trainer supports the users. Your SAP team carries out or approves the transports and receives the alerts with us.

    What you provide

    • A deployment window approved with your SAP team.
    • The necessary production access, in line with your security rules.
    • The contacts who should receive alerts and handle incidents.

    What you receive

    Solution in production, runbook and maintenance plan

    Your approval

    Flows run without manual re-keying.

Our commitments

A collaboration designed to stay under your control.

01

Transparency

You see progress, decisions, risks and next steps without waiting for a crisis meeting.

02

Continuous validation

Key choices are demonstrated and approved along the way rather than discovered at delivery.

03

Verifiable quality

Every outcome is tied to concrete criteria for functionality, security, performance or adoption.

04

Knowledge transfer

Documentation and onboarding are part of the engagement, so you never depend on us unnecessarily.

First step

Let's start by understanding your situation.

Tell us about your project, even if it's still vague or already in trouble. Together, we'll find the safest place to start.

Tell us about your project