Engagements
The shape of an OakCore engagement: scoping, workshops, delivery rhythm, and what you own at the end.
A predictable arc for uncertain integrations
Consulting engagements fail when the method is vague. OakCore uses a repeating structure so your team always knows what week you are in.
Scoping call
Thirty minutes to confirm systems, deadlines, and whether we are the right fit. No proposal theatre — if we cannot help, we say so.
Written proposal
Scope, exclusions, indicative timeline, and fee. Deposit terms follow our refund policy.
Discovery & inventory
Interviews, endpoint inventory, and a draft contract map. Gaps in ownership are listed as risks, not buried.
Design & review cycles
Workshops with your engineers, interface reviews, and spike guidance. Your team implements; we stay accountable for the design decisions.
Cutover window & handover
Agreed support window for first production traffic, then a handover pack: decisions, open risks, and backlog suggestions.
What you provide
Named owners for each system, access for read-only review where needed, and a product counterpart who can decide scope trade-offs. Without those, engagements stall — we will pause rather than invent decisions.
What you keep
All artefacts produced for your engagement — contract maps, decision records, runbook drafts — remain yours. OakCore does not lock work behind a proprietary platform.