Our Approach | How an Infoseer Engagement Runs | Infoseer Consulting

How an engagement runs, stage by stage

Six stages, each with a named deliverable and a defined exit. Below each one you will also find what we need from you, so nothing stalls waiting on an approval nobody knew was required.

The six stages against a calendar Typical reporting engagement
The six stages against a calendarA timeline chart. The discovery call is a 30 minute slot on day one. The fixed-price proposal follows within 48 hours. After approval, kickoff and data access happen in week one, build and review run through week four, delivery and handover fall in the final week, and ongoing support continues afterwards and is optional. Day 1 Day 3 Week 1 Week 2 Week 3 Week 4 Onward 01 Discovery call 02 Fixed-price proposal 03 Kickoff and data access 04 Build and review 05 Delivery and handover 06 Ongoing support AI: 2 to 6 you approve, then access is granted Stage 1 is 30 minutes and costs nothing. Nothing else starts until you have a fixed price in writing.
AI pilots run longer, usually two to six weeks. Everything before the approval line costs you nothing.
  1. 01Day 1, 30 minutes, no cost

    Discovery call

    We ask about the decisions you are trying to make, who needs the answer, and which systems hold the data. No pitch, no slides.

    You get

    A written summary of what we heard, and an honest read on whether this is work we should do.

    From you

    Whoever owns the problem, on the call. No preparation needed.

  2. 02Within 48 hours of the call

    Fixed-price proposal

    Scope, named deliverables, timeline, price, and what sits outside the scope. If a smaller project is the right answer, that is what we propose.

    You get

    A proposal with a fixed price and a stated exclusion list. No open-ended retainer unless you ask for one.

    From you

    Review at your pace, and one approver who can say yes.

  3. 03Week 1 after approval

    Kickoff and data access

    Requirements are confirmed in one session, then source systems are connected under accounts your IT team issues. The access process is set out below.

    You get

    A confirmed requirements list, a data access register, and connected sources you can verify.

    From you

    Someone who knows the source systems, and read-only credentials for the tables in scope.

  4. 04Weeks 1 to 4, or 2 to 6 for AI work

    Build and review

    Work lands in short cycles. You see a preview each cycle and comment before anything reaches production. Revisions inside the agreed scope are included.

    You get

    A working preview per cycle, and a short note on what changed and what is next.

    From you

    About two hours a week to review, and a decision on anything that turns out to be ambiguous.

  5. 05Final week of the project

    Delivery, training, and handover

    The solution goes live with a walkthrough for the people who will use it, documentation of how it works, and 30 days of support included.

    You get

    A live solution, a handover pack, a recorded walkthrough, and 30 days of post-delivery support.

    From you

    The users, in one training session, and confirmation that the deliverables are accepted.

  6. 06Ongoing, optional

    Ongoing support

    A monthly retainer covers maintenance, new data sources, and a quarterly review. It is optional by design and can be cancelled at any time.

    You get

    A named contact, agreed response times, and a quarterly session on what to build next.

    From you

    Nothing, unless you want changes. Access stays revoked until you re-enable it for a request.

Data security and access

Access is granted, not requested informally

Everything we build runs inside your own environment, under accounts your IT team controls. You can see who has access, to what, and until when, and you can revoke it without calling us.

We sign your non-disclosure agreement before the first working session, or provide ours if you prefer. Data processing terms and retention are agreed in writing before any system is connected.

Named accounts in your tenant
Each consultant gets an individual account issued by your IT team, inside your Microsoft tenant. No shared logins, and no credentials passed over chat or email.
Read-only and scoped
Access is read-only wherever the work allows, and limited to the specific tables, folders, or workspaces named in the access register.
Nothing copied to personal machines
Production data stays in your environment. Where a sample is needed for development, it is masked or synthetic and agreed in advance.
Sensitive fields excluded by default
Personal identifiers, account numbers, and salary data are left out of reporting models unless a specific requirement needs them, with row-level or column-level security applied.
Revoked at handover
Access ends when the engagement does. Under a retainer it is re-enabled per request rather than left standing.

Common questions

Working together

See what we deliver in capabilities, or which sectors we know best in industries.

What do we need to provide?

One decision maker who can approve scope, one person who knows the source systems, read-only access to those systems, and about two hours a week for review during the build.

What happens if the scope changes mid-project?

Changes are written up as a short addendum with their own effort and price before work starts. The original scope continues in parallel, so a new request does not quietly move the delivery date.

How does Infoseer access our data securely?

Through named accounts your IT team issues inside your own tenant, read-only wherever possible and scoped to the tables in the access register. Nothing is copied to personal machines, and access is revoked at handover.

Stage one takes 30 minutes

Bring one decision that is hard to make today. You will leave the call knowing what it would take to make it reliably.