How we work

Start with the process. Define success. Keep people in control.

Wiko starts by understanding how work happens today. We agree on what needs to improve, evaluate the evidence, and define the controls needed before putting a workflow into operation.

The route depends on your situation. You don’t need to purchase every service, and an assessment may show that a process change or an existing tool feature is the better next step.

Tell us about your process

Before a project begins

A clear first step

Share a brief description of your process and the problem you want to address. Additional context is optional.

Exceiver Saenz personally reviews requests and responds with the next step within two business days. If there’s a fit, he sends a booking link for a free conversation of up to 30 minutes.

That conversation helps us understand your stated problem and discuss a suitable route. It is preliminary; it does not include a detailed assessment, custom development, or a formal evaluation against a baseline.

Before contracted work begins, we agree on scope, deliverables, responsibilities, pricing, timing, and acceptance conditions in a proposal and contract.

1. Understand

Understand the work before choosing a solution

We review how the process works, where repetitive tasks occur, and which decisions, handoffs, and exceptions matter. We compare the reported problem with available evidence rather than assume the cause.

Discovery is part of every project. Its depth depends on the scope: a new opportunity may need a broader assessment, while an existing workflow may need a focused review.

What you contribute: process knowledge, available records you are authorized to share, relevant stakeholders, and your priorities and constraints.

What we establish: a shared understanding of the problem, missing information, and a grounded next step. The recommendation may be to investigate, test, improve an existing process, or avoid an unnecessary implementation.

2. Assess & Validate

Agree on how improvement will be evaluated

We define the starting point, the main measure of success, and the quality and risk limits that a solution must respect. Depending on the problem, measures may include manual time, rework, completion time, or throughput.

When the baseline cannot yet be measured reliably, we document the uncertainty and agree on how to resolve it. Where a proposed solution needs validation, a limited experiment can test representative cases and reveal failures and exceptions.

What you contribute: agreement on success criteria, representative cases, authorized test access, and review of findings with the relevant decision-makers.

What we establish: evidence and limitations sufficient to decide whether to continue, adjust, test further, or stop. A separately contracted PoC is not required when sufficient validation already exists; discovery and acceptance testing still apply.

3. Implement

Build for normal work, exceptions, and handoff

We design and build the agreed workflow, connect the required systems, and define rules for human review, approval, and escalation. Testing covers representative cases, permissions, integrations, exceptions, and recovery—not just successful executions.

Before delivery, we verify the agreed acceptance criteria and risk limits. We document how to operate, supervise, pause, and recover the workflow, then train the designated operators and transfer responsibilities as agreed.

What you contribute: an authorized project owner, required accounts and permissions, review of business rules, participation in acceptance testing, and people available for training and handoff.

What we establish: documented acceptance results, operating instructions, human controls, and an assigned operational owner. Ownership, access, licenses, infrastructure, and third-party costs are defined in the agreement.

Full Workflow Implementation includes 30 calendar days of initial corrective support from documented formal acceptance. Covered defects attributable to Wiko reported during that period remain covered until resolution, even if correction finishes later. Documented pending commitments remain in force.

4. Operate & Improve

Assign ownership and evaluate changes with evidence

An operational workflow needs an owner, monitoring, and a way to handle exceptions and failures. These responsibilities may sit with your team or Wiko, depending on the services agreed.

Managed Automation provides contracted technical monitoring, maintenance, and incident handling. Continuous Optimization investigates whether specific changes offer worthwhile improvement. Coverage, response times, responsibilities, and approval requirements are agreed explicitly.

What you contribute: designated supervisors, business decisions on escalated cases, maintained permissions and accounts, and approval of changes to rules or accepted risk.

What we establish: clear operational responsibilities and, when optimization is contracted, documented experiments and recommendations. Evidence may support keeping the current workflow unchanged.

Implementation also includes a subsequent review, with timing, scope, participants, and responsibilities agreed in the proposal and handoff. This review does not imply ongoing management or deeper experimentation at no additional scope.

Your role and Wiko’s role

Clear responsibilities throughout the work

Area	Wiko	Your team
Process and scope	Investigate the process and document the agreed work	Explain the process, priorities, and constraints
Measurement and testing	Define methods and report findings and limitations	Agree on criteria and validate business relevance
Data and access	Use authorized access within the agreed scope	Authorize appropriate access and define permitted uses
Human decisions	Define review and escalation routes	Make domain decisions and approve exceptional cases
Operation	Deliver the handoff or provide contracted technical management	Assign an owner and maintain client-controlled systems
Changes	Recommend and implement changes within scope	Approve changes affecting business rules, risk, or scope

When something goes wrong

Make exceptions visible and give people a way to act

We define how failures are detected, which cases need escalation, who responds, and how the workflow can be paused or recovered. Execution records support review within the agreed scope.

An incorrect AI result is evaluated against the agreed criteria, test coverage, and controls; it is not automatically treated as a covered defect or dismissed because AI is involved.

When missing information, permissions, approvals, or other dependencies block progress, we identify what is needed and communicate the effect on scope or timing. Material changes are agreed before proceeding.

Common questions

Do we have to start from scratch?

No. Discovery can focus on your existing workflow and whether it should be maintained, corrected, expanded, replaced, or tested further.

Does a successful PoC mean we are ready for production?

Not by itself. Production requires the agreed design, controls, acceptance testing, operating documentation, and responsibilities.

Who makes business decisions?

Your team retains authority over business rules, domain judgment, and accepted risk. We define the technical behavior and human control points within the agreed scope.

Do you guarantee savings or error-free automation?

No. We define how results will be measured, report limitations, and evaluate outcomes against agreed criteria. Estimated benefits remain estimates until demonstrated.

Closing invitation

Start with the work you want to improve

You don’t need a technical specification to make an initial inquiry. Tell us what your team does today, where repetitive work creates a burden, and what you would like to change.

Tell us about your process Explore our services