HOW WE WORK TOGETHER
Choose a starting model based on how well the requirement is understood. Scope, commercials and responsibilities are confirmed in a written proposal; this page is an explanation, not a binding offer.
Best when the process, feasibility or integration is not yet clear. Agree a bounded assessment or proof of concept, sample data, questions to answer and an output such as a process map, recommendation or demonstrator. A pilot is not automatically a production system.
Best when requirements and acceptance criteria are sufficiently defined. Agree deliverables, assumptions, dependencies, milestones and a project fee in writing. Requests outside that baseline follow an agreed change process; a fixed price does not mean unlimited changes.
Best when priorities will evolve. Agree rates, roles, reporting, review points and a budget or approval limit. Work is billed on the agreed basis with visible progress and effort records. New budget authority is confirmed before exceeding an agreed limit.
Best for an existing Business Central environment, integration or application needing agreed support. Assess the system first, then define coverage, hours, included effort, exclusions, escalation and service targets. No 24/7 coverage or guaranteed response is implied by this website.
BEFORE WORK STARTS
Deliverables, what is excluded, acceptance scenarios, review periods and the process for resolving defects or requesting changes.
The charging model, milestones, payment terms, taxes where relevant, and responsibility for licences, hosting, connectors and model usage.
Client contacts, required permissions, sample data, decisions, environment readiness and dependencies that affect delivery dates.
Ownership and access for custom work, pre-existing components, open-source or vendor licences, repository handover and any conditions on transfer.
Permitted data, access controls, approved providers, confidentiality obligations, processor terms where applicable and secure transfer methods.
Deployment responsibilities, backups and rollback, any agreed defect-remedy period, support coverage, exit and handover arrangements.
Ownership of custom work and access to source code must be agreed in writing. Third-party and pre-existing components may carry separate licences. Do not assume a website enquiry transfers intellectual property.
Yes. A bounded discovery or pilot is often a useful first step before a larger implementation. Its price, duration and outputs are agreed after discussing the requirement.
No. This page explains engagement options. A signed proposal, statement of work or other applicable agreement defines the actual obligations. It does not replace tailored legal terms.
START WITH A CONVERSATION
Share the process, systems involved and what a useful outcome would look like. We will assess scope, dependencies and the right starting engagement.