Advisory call

Bring one problem. We will tell you if it is worth building.

Thirty minutes with the engineers who would do the work: not an account manager taking notes to relay later. You leave with a straight read on feasibility, the sequence we would follow, and what a first build would actually take. Including, sometimes, that you should not build it at all.

Book it

Tell us enough to bring the right people

The more specific the problem, the more useful the call. If you are not sure which category you fall into, say so. That is a legitimate answer and we have a option for it.

First name *

Last name *

Work email *

Phone optional

Company *

Your role *

What do you want to talk about *

Region optional

Organisation size optional

The problem, in your own words the most useful field on this form

How did you hear about Innopas optional

We reply within one business day

Who joins

Engineering, not sales

Whoever would actually run the work, plus a sector advisor when the problem is in energy, banking, healthcare, public sector or aerospace.

What it costs

Nothing, and no discovery invoice

Thirty minutes, video call. If we need a second conversation to be useful, that one is free too. Paid work starts when there is something worth scoping.

What you leave with

A straight read

Whether the problem is solvable with what exists today
Whether it needs research first, or is an engineering job
The sequence we would follow, and where the risk sits
A rough shape and size for a first build

Prefer email

Write to us instead

reachus@innopas.com — or see all three offices. Monday to Friday, 9am to 5pm.

What happens

Three steps, and none of them is a proposal

Most first calls in this industry end with a document that takes three weeks to arrive and says what could have been said on the call. We would rather use the thirty minutes properly.

BEFORE

We read what you sent

Your problem description decides who joins the call. If it needs a research view we bring one; if it is a platform question we bring the person who built it.

You do nothing else to prepare.

ON THE CALL

We ask about constraints, not budget

What data exists, what cannot move, who has to approve it, what has already been tried. The constraints determine whether this is buildable far more than the budget does.

30 minutes, and we keep to it.

AFTER

A short written read

A page: what we think, what we would sequence first, and what we are unsure about. If we are not the right people, it names who might be.

Within a few days, not a few weeks.

HONESTLY

Sometimes the answer is no

If the data is not there, the timing is wrong, or an existing product already solves it, we say so. A call that saves you a bad two-year programme was worth thirty minutes.

We would rather lose the work than be the reason it failed.