Compare the scope.
Then the price.
A chatbot demo and a controlled integration into business operations are not the same purchase. Use these questions to understand what an AI implementation quote includes—and what it leaves with your team.
An illustrative workflow. Permissions and approval points are agreed for each implementation.
Five things that change the work
Systems and interfaces; the condition of the records; permissions and approval steps; failure and recovery requirements; and ongoing monitoring and support. Model usage is only one part of the cost. Nordlith scopes the actual workflow before offering a project price.
Read-only support or transactional change?
An assistant that prepares a briefing can be contained differently from a workflow that changes stock, customer records or a schedule. The latter needs stronger identity matching, authorisation, readback and recovery. Ask which actions are included and which remain manual.
What to ask every provider
Which systems and subscription tiers are assumed? Who owns the data mapping? What happens when the interface changes? Who reviews exceptions? How is a result verified? What operating notes and support are included? A clear answer is more useful than a broad promise of transformation.
Separate build cost from running cost
Clarify hosting, model/API usage, third-party subscriptions, monitoring and maintenance. Ask who holds each account and what usage limits apply. No fixed price, hosting location or vendor entitlement is implied by this guide.
Use a bounded first workflow to reduce uncertainty
A smaller scope can test feasibility and reveal the true exception burden before a wider commitment. Agree the deliverable, acceptance evidence and recovery method first. A pilot should inform a decision; it should not become a permanent demonstration with no operating owner.
Before we start.
Do you publish a fixed package price?
No fixed price is represented here. Tell us the workflow, systems and approval needs so the scope and commercial terms can be assessed honestly.
Is ongoing model usage included?
That depends on the agreed arrangement. Build, hosting, API usage and support should be separated explicitly in a proposal.
Can you guarantee a return on investment?
No. Establish a baseline and measure the operational effect after release. A feasibility assessment or useful first workflow does not guarantee savings or revenue.
A useful next step.
What would be easier
if this worked properly?
Tell us where time or follow-through is being lost. We will start with the problem, not a product pitch.
Talk to Nordlith →