We understand your needs before preparing a scoped quote. Future proposals are in USD; scope, deliverables, timing and terms are agreed separately. An enquiry is non-binding, not a purchase or booking.
Engagement models
Engagement options, confirmed in a written scope.
Each engagement is quoted after understanding your needs. Tax treatment, scope and availability require written agreement. We do not list service prices or budget bands. Future proposals are in USD, after understanding your needs.
Start here
Architecture teardown
Scoped quote
Review scope and availability agreed separately
A structured read on your system, data model and AI surface. Potential outputs include observed risks, open questions and next-step recommendations, as agreed in scope.
- Pre-read of your current architecture or product plan
- Live session: failure modes, data model, sequencing
- Written summary with prioritised decisions
- An honest answer on whether you need us at all
Find the work
AI opportunity audit
Scoped quote
Discovery scope and timing agreed separately
We shadow one department, map how work really moves, rank automation opportunities and model the return. Deliverables, access, timing and commercial terms are agreed separately.
- Interviews and live shadowing of the people doing the work
- Documented-vs-real process map with every exception
- Ranked opportunities with autonomy level and risk
- Business case with a baseline and a stop rule
Ongoing
Fractional architect
Scoped quote
Advisory responsibilities and terms agreed separately
Senior architecture attached to your team without a full-time hire. Design authority, review, and the security posture your enterprise buyers ask for.
- Target architecture and decision records
- Working-session frequency agreed with your engineers
- Review authority on schema, AI and integration choices
- Security and compliance posture for enterprise deals
Delivery
Build and run
Scoped quote
Release scope and acceptance agreed separately
We scope discovery and release work. Operating support, staffing and handover are separately agreed.
- Discovery and target architecture
- Production build with AI surfaces and audit trails
- Deployment, observability and security hardening
- Operating support and documented handover as agreed
Selective partnership structures may be discussed separately; no equity, cash-expense, control or availability terms are established here.
What shapes the quote
Review scope, integrations, acceptance, security and operating responsibilities.
Regulatory boundary
CMMC, HIPAA or SOC 2 work carries evidence, enclave and review overhead. It is real engineering, not paperwork, and it changes the number materially.
Data model condition
A mismatch between the domain model and business process can add migration and delivery cost. Compare it with other scope and operating constraints.
Integration surface
Each external system — banking, identity, ITSM, EHR — adds contract, failure and test cost that scales faster than feature count.
AI autonomy level
Assisted AI is a feature. Agent-run AI needs authority boundaries, evaluation and audit trails. Moving one rung up the ladder is a phase, not a sprint.
Before any invoice
Items to clarify before any invoice.
- Discovery calls, proposals and scoping conversations.
- Review scope, proposed outputs and availability.
- Responsibility for rework and any remedy in the signed agreement.
- Handover deliverables and their inclusion in the written scope.
What each person receives
User
Department head / COO
Needs: A system that matches how the team actually works, not how the vendor imagined it.
Doubt: Custom software sounds slow, risky and hard to maintain.
Proposed deliverables · agreed in scope
- • A mapped real-vs-documented process
- • A running system for one department
- • Runbooks the team can follow
Buyer
CFO / finance lead
Needs: A cost case that holds against current seat spend and manual hours.
Doubt: The return will be asserted, not measured.
Proposed deliverables · agreed in scope
- • A baseline agreed before work starts
- • A 3-year rent-vs-own comparison
- • A measured result against that baseline
Approver
IT / security lead
Needs: Something supportable that does not add shadow IT.
Doubt: Another system the IT team will be left holding.
Proposed deliverables · agreed in scope
- • Architecture and data model documentation
- • Access control and audit design
- • A named handover plan
Affected
The team doing the work
Needs: Less re-keying and fewer workarounds.
Doubt: Automation will be imposed without asking them.
Proposed deliverables · agreed in scope
- • Shadowing time where their workarounds are recorded
- • Clear lines on what stays human
Access we ask for — and how you take it back
- • Read access to the department's tools and exports
- • Shadowing time with named team members
- • No production write access during the audit
Access is limited to the department in scope and logged.
Initial inquiry: non-sensitive summary only. Later assessment: authorised redacted samples or read-only access. Sandbox and production write access require separate approval, minimisation, access expiry and retention agreement.
Agree revocation, working-copy handling, retention exceptions and confirmation responsibilities before access.
Next step
Get the teardown first, decide afterwards.
Discuss your needs before any quote. Scope, availability and terms require separate agreement; this enquiry is not a booking.