Start with a concrete problem
A task that takes too long, missing software or a manual that is not progressing is enough for an initial discussion. The tools used and desired result are then examined with you.
Before deciding: scope and limits
The first discussion establishes the difficulty.Read moreShow less
The first discussion establishes the difficulty. Prepare an example task or document, the expected result, tools used and your deadline. An indicative budget helps choose a suitable first step. No password or confidential file is needed in this first message.
If a diagnosis or trial is needed to price the next stage, its scope and cost are explained before starting it. The proposal distinguishes initial work, deliverables, checks, any licences and recurring costs. Exclusions and unresolved points are written down.
The schedule identifies dependencies on access, sources and your approvals. A change in scope prompts a discussion of cost and timing before implementation. You can start with a limited package, examine the result and decide on the next stage.
Availability, support arrangements and coverage limits are agreed in the engagement.
Entrust your IT management
For an existing estate, an assessment precedes defining support.Read moreShow less
For an existing estate, an assessment precedes defining support. Endpoints, servers, the network, backups and telephony are inventoried. Initial improvements, interventions and recurring management are distinguished in the proposal.
Define what will be delivered
Initial work can be limited to an audit, a few manual pages, a data exchange or a prototype.Read moreShow less
Initial work can be limited to an audit, a few manual pages, a data exchange or a prototype. The deliverable, necessary information and planned checks are specified in the proposal.
Understand the price
Preparation, implementation and checks are priced for the project.Read moreShow less
Preparation, implementation and checks are priced for the project. Hosting, subscriptions and maintenance are listed separately when needed. Extensions are agreed before they are carried out.
AI can accelerate certain tasks. Time spent preparing data, connecting tools and checking results must also be included.
Set a realistic schedule
Available documents, technical access and people responsible for approval are identified.Read moreShow less
Available documents, technical access and people responsible for approval are identified. An initial usable result can be planned before all functions are complete.
Prepare your independence
Read moreShow less
Getting started is supported. Agreed instructions, sources or exports are handed over. Maintenance and assistance can continue according to your needs.
Prepare the first discussion
Describe what you do today, the difficulty and what you would like to obtain.Read moreShow less
Describe what you do today, the difficulty and what you would like to obtain. You can specify your deadline and budget. A description is enough to begin; sensitive documents can later be exchanged under suitable conditions.
Your questions
Yes.Read moreShow less
Can we start with a small project?
Yes. One task or a sample of documents can be the starting point. Its price mainly depends on preparation, tools to connect and necessary checks.
Must we change all our tools?
Your current tools are examined first. Connecting two applications or targeted automation may be enough.
Will I be able to use the solution independently?
Getting started and instructions are planned within the project. Desired independence and remaining assistance are defined together.
What if we want to change provider?
Sources or exports handed over, code rights and required licences are specified in the proposal. Handover conditions are known before work begins.