Four ways to start. One boundary for each.

Zanatello Acosta Consulting (ZAC) works in four engagement modes, not a catalogue. Each one has a buyer situation, a set of outputs and a line it does not cross.

Engagement modes

SRV.01–04

01DiagnoseSystem and opportunity audit

System and opportunity audit

For teams that know something is inefficient but not where value is lost. ZAC maps how the work actually runs, finds where time, money and decisions leak, and ranks what to change first.

BoundaryDiagnose recommends; it does not build. It ends with a scoped first intervention you can take forward with ZAC or anyone else.

What you get

Current-state map
Prioritised opportunity register
Recommended first intervention
Scoped roadmap

Activities

Stakeholder interviews
Process and tool mapping
Bottleneck and handoff analysis
Data and decision-flow review
AI and automation screening
Risk, effort and value prioritisation

02DesignProduct and workflow blueprint

Product and workflow blueprint

For teams that need to turn an opportunity into a buildable system. ZAC turns the chosen opportunity into a validated concept, a prototype or workflow model, and a specification a developer can build from.

BoundaryDesign specifies and prototypes. Building it for production is a separate, scoped step.

What you get

Validated concept
Prototype or workflow model
Functional and technical specification
Delivery plan

Activities

Product discovery and service design
Requirements
UX flows and interactive prototypes
Solution architecture
KPI and operating-model definition
Build-versus-buy analysis

03BuildApplied systems delivery

Applied systems delivery

For teams that need a focused tool, automation or prototype built. ZAC builds the smallest system that resolves the friction, tests it with the people who will use it, and hands it over documented.

BoundaryBuild covers focused tools, automations and prototypes. For larger platforms, ZAC leads definition and delivery and coordinates named specialists.

What you get

Working tool or automation
Documentation
Handover

Activities

Internal tools and operational interfaces
Workflow automation
AI-assisted processes
Data workflows and reporting
MVPs and prototypes
Coordination of external developers
Testing, documentation and handover

04EmbedFractional product and operations partner

Fractional product and operations partner

For teams that need senior product and operations support for a defined period. ZAC provides roadmap stewardship and decision support on a fixed schedule, for a fixed term, with named deliverables.

BoundaryA fixed term, for example three or six months, with named deliverables and a review date. A set number of days per month, scheduled by ZAC. ZAC recommends, prepares and coordinates; your leadership decides. No line management, signing authority or budget ownership. ZAC works with several clients.

What you get

Recurring review cadence
Maintained roadmap
Specifications and decision papers
Improvement pipeline

Activities

Roadmap stewardship
Product and project coordination
Operational review cadence
Requirements and delivery governance
Continuous-improvement pipeline
Decision support for leadership

Embed, in detail

SRV.04

A senior partner for a defined period.

Embed is a service delivered by an independent business. It is time-boxed, capacity-based and advisory, and every proposal says so.

Fixed term: For example three or six months, with named deliverables and a review date.
Days per month: A set number of days, scheduled by ZAC. Capacity, not availability on call.
Advisory: ZAC recommends, prepares and coordinates. Your leadership decides. No line management, signing authority or budget ownership.
Own methods: ZAC works with its own methods and tools and invoices against the agreed scope.
Non-exclusive: ZAC works with several clients at the same time.

Plain answers

SRV.05

What buyers ask first.

Can one independent consultant handle this?: Bruno leads diagnosis, definition, prototyping and coordination, and brings in named specialists only when a scope needs them.
Strategy or implementation?: Both. The boundary is stated for each engagement, in writing, before it starts.
Is this only about AI?: No. AI is one possible component inside a better system.
Will we become dependent on ZAC?: The default is documented systems, transparent tools, repositories you own and an explicit handover.
Is the work local?: ZAC is based in Norway. Remote by default, on site when it helps.
Where is the evidence?: In short cases with context, intervention and measured result, each labelled by where the work was done.

Choose a starting point More questions