Engagements
Scope the work. Know what you receive.
Engage LEXKIT for architecture and planning, a defined implementation, or ongoing operation and improvement. We shape the work around your systems, priorities and team, then document the deliverables, responsibilities and commercial terms.
Discuss your architectureExplore the service catalogueThree ways to engage
Choose the work your team needs.
Architecture and planning
Make the key decisions before committing to implementation.
What you receive
- Current-state systems and workflow map
- Source and ownership register
- Target architecture and options
- Prioritized implementation scope and acceptance criteria
Receiving ownerYour sponsor and technology lead receive the architecture brief and decide the delivery sequence.
Build and integrate
Deliver the software, connections and workflows agreed in scope.
What you receive
- Custom software or configured work interfaces
- Agreed integrations and data flows
- Realistic acceptance and recovery checks
- Delivery documentation and operating handover
Receiving ownerYour system owners review the boundaries; the service owner accepts the implementation and runbook.
Operate and improve
Keep responsibilities clear as the technology and business change.
What you receive
- Defined maintenance and operating scope
- Release and change-review responsibilities
- Runbooks and improvement priorities
- An agreed reporting and review cadence
Receiving ownerYour operating lead and LEXKIT delivery owner agree responsibilities, escalation and the next improvement decisions.
From inquiry to handover
A clear path through the work.
Architecture conversation
Describe the business outcome, current systems and the people involved. We identify the main dependencies and the work needed to establish scope.
What this stage establishesA clear problem, accountable sponsor and useful next step.
Scope and proposal
We define the deliverables, source and system boundaries, responsibilities, acceptance criteria and commercial terms.
What this stage establishesA written scope your business and technical owners can assess.
Delivery and review
The team works through the agreed architecture or build sequence. Named owners review decisions, deliverables and exceptions at the relevant handoffs.
What this stage establishesAcceptance findings and any remaining decisions are recorded.
Handover and next phase
Your operating team receives the agreed documentation, ownership and runbooks. We review ongoing work and additional priorities with your sponsor.
What this stage establishesThe receiving team understands what it owns and how the next phase is scoped.
What shapes the scope
The detail behind a useful proposal.
- Business scope and dependencies
- The processes, teams and outcomes involved, including work that must be coordinated with other projects or vendors.
- Systems and integration effort
- Interfaces, custom engineering, source formats, legacy dependencies and the changes needed to connect them.
- Data and knowledge readiness
- Source quality, ownership, permissions, normalization and the work required to make information useful.
- Deployment and operating model
- Environments, access boundaries, release responsibilities and the people operating each component.
- Review and acceptance
- The scenarios, specialist review and evidence needed for the receiving team to accept the delivery.
- Ongoing responsibilities
- Maintenance scope, change management, reporting, escalation and the review cadence agreed for continued work.
Working together
Bring the right people into the scope.
A strong starting point
- A business outcome with a sponsor who can set priorities.
- System and data owners available to make scope decisions.
- A team ready to review deliverables and accept the handover.
Prepare for the conversation
- The process or systems you need to connect.
- The business and technical owners involved.
- Known dependencies, constraints or timing considerations.
- The work product or operating change your team needs.
The written agreement
Make the responsibilities explicit.
- Deliverables and their acceptance criteria.
- System, source and implementation boundaries.
- Delivery owners and receiving teams.
- Commercial terms and the treatment of scope changes.
Start here
Tell us what needs to work together.
Describe the operating challenge, the systems involved and the outcome your team needs.
Discuss your architectureFAQ
Scoping the engagement.
How is an engagement priced?
We price against the agreed work, dependencies, deliverables and responsibilities. Discovery establishes the scope needed for a written proposal.
Can we commission architecture without implementation?
Yes. Architecture and planning can be a distinct engagement with a systems map, target architecture and implementation priorities your team can act on.
Can LEXKIT deliver a defined build?
Yes. Build and integration engagements specify the software, interfaces, workflow, acceptance criteria and handover included in the delivery.
How is ongoing work arranged?
We agree the maintenance, operating and improvement scope with the responsible team. The proposal sets the responsibilities, review cadence and commercial terms.
What happens when requirements change?
We document the change, its dependencies and its effect on the scope. The responsible sponsor approves the next step before the additional work is added.
What follows the first inquiry?
We review the operating challenge and identify the right architecture discussion. That conversation establishes the information and decision-makers needed to shape a useful scope.