From the first workflow to the team that runs it.

Start with a concrete piece of work

A weekly planning spreadsheet. A request waiting for approval. A report that takes too long to assemble. The first conversation starts with a task somebody actually performs. Its inputs and outputs help establish the data, connections and interfaces required.

Begin at the stage you need

Engagement	What we produce together	Decision at the next stage
Discovery and pilot	Current workflow, representative data, a working task and validation findings	Is it useful to the operator, and are the conditions for further investment clear?
Implementation	Business models, interfaces, integrations, migrated data and operating documentation	Can the agreed work be completed and its exceptions handled?
Ongoing operations	Service and usage reviews, incident response, change plans and improvement records	Are operational issues and the next changes assigned to accountable owners?

Pilot scope and timing depend on data readiness, connection access and review availability. Example schedules in the proposal tool are considered separately from the project delivery date.

Define the service beyond go-live

Ongoing support can cover the required combination of infrastructure, applications, data connections and AI execution. A server can be healthy while a stopped data feed leaves planners working from old information. The operating scope should therefore include data freshness, failed tasks and the people responsible for resolving them.

Area	Customer decisions	Scope to agree with Giz
Business workflow	Priorities, policy, approvers and acceptance	Model, interface and automation implementation
Data and access	Source ownership, access authority and security policy	Mapping, integration configuration and reconciliation
Service operations	Coverage, impact levels and change approval	Observation, incident analysis, response and recovery
Infrastructure and models	Deployment, resources and external service terms	Installation, updates, capacity and usage management
Handover	Internal operators and training participants	Agreed source, configuration, documentation and practice

State response commitments, recovery objectives, third-party dependencies and out-of-hours coverage in the contract.

Review scope and cost in one proposal

Use the tool below to work through goal → scope and readiness → effort and cost → proposal review. Read the deliverables and completion criteria first. Then adjust role-based effort and expenses to calculate an indicative estimate using the displayed reference rates.

If effort is still unknown, generate an AI scope and effort draft. Review its assumptions and unanswered questions before applying it. A binding estimate follows review of real requirements and integration conditions, including the treatment of licenses, model usage, infrastructure and operations.

Prepare the current workflow, representative inputs and outputs, and a data owner. Save the proposal for review or send it to the team to define the next engagement.