Scope document
Deliverables, exclusions, acceptance criteria, assumptions and dependencies.
Issued before production
Process
How a KalkiWebproject runs
Every project follows six documented stages, from first conversation to handover. Clients can see decisions, risks and test results as work progresses.
01
Discovery
What the business needs to achieve, who must use it, what already exists and how success will be measured.
02
Scope & specification
Deliverables, exclusions, dependencies and acceptance criteria are documented. Where scope supports it, price is fixed; any change is agreed before it affects time or cost.
03
Design
Content, layout, interaction and motion are resolved as a system, then tested against real copy and real device constraints.
04
Build
A staged version is available from the first meaningful milestone. Performance, accessibility and maintainability are checked throughout.
05
Test & verify
Critical journeys are checked across supported browsers, keyboard and representative assistive technology. Form delivery, links and agreed performance measurements are recorded.
06
Handover
Documentation, credentials, source code and a practical walkthrough. Client-owned accounts from the outset, with no locked keys or avoidable dependency.
Project visibility
From brief to handover
Clients can see decisions, risks and test results at each stage
Project artefacts
Documents supplied at each gate
These working documents define what will be built, what passed and what the client owns after launch.
Verification report
Browser matrix, accessibility findings, performance and critical journey results.
Delivered before launch
Handover checklist
Every item transferred at close-out, including account and repository ownership.
Completed at handover
Project enquiries
Tell us what you need to build
Share the goal, budget and timing. We will reply within one business day with the next practical step.