Welcome to Kiluth Docs
Kiluth’s internal documentation site. Your central hub for operational guidelines, standards, and processes across all departments.
New here? See How We Work — a project from first contact to maintenance, with each stage linked to the guideline that runs it.
Departments
| Department | Purpose | |
|---|---|---|
| 1 | Account Management | Owns commercial and client relationship workflows: sales, account execution, scope/proposal coordination, and client support |
| 2 | Delivery | Owns project management and delivery checkpoints: resource allocation visibility, QA coordination, client acceptance, and closure |
| 3 | HR | Owns people operations: onboarding, training, people policies, and employee support |
| 4 | Technology | Owns engineering delivery and technical operations: architecture, development, DevOps, security, deployment, and incident response |
| 5 | Creative | Owns creative production and design execution: brand assets, visual/media, UX/UI, content, and copy |
| 6 | Finance | Owns invoicing, payments, accounting support, and procurement operations |
| 7 | Legal | Owns contracting, change orders, compliance, and facilities operations |
| 8 | Marketing | Owns lead generation, brand/PR, and handoff to Sales |
How We Work
The full client pipeline — how Kiluth takes a client and their product from first contact to maintenance. Each stage links to the guideline that runs it.
| # | Stage | What happens | Guideline(s) |
|---|---|---|---|
| 1 | Lead in | Marketing logs the lead and hands it to Sales, who qualifies it | Lead Intake & Handling · Lead Qualification |
| 2 | Scope & price | Meet the client, get scope sign-off, estimate the work, and turn an accepted proposal into a deal | Scope Definition & Price Assessment · Pre-Activation Estimation · Client Onboarding Pack |
| 3 | Contract & deposit | Sign the contract; invoice and confirm the deposit before any work starts | Contracting & Change Order · Invoicing & Payment Operations |
| 4 | Build | Sprint delivery through UX → UI → Dev handoffs, each frozen by a client sign-off | Delivery Production & Resource Allocation · UX Workflow · UI Workflow |
| 5 | Changes after sign-off | A change after any sign-off is a Change Request — priced, signed, and paid before rework | Change Request Workflow |
| 6 | UAT & go-live | Client acceptance testing, acceptance sign-off, go/no-go, then go live | Client Acceptance (UAT) & Go-Live |
| 7 | Closure & handover | Confirm final acceptance, deliver the handover package, and record closure | Project Closure & Handover |
| 8 | Maintain | Warranty, then Maintenance Agreement and hosting — tracked in ERPNext for renewal | Maintenance & Hosting |
The rules that always hold
| Rule | |
|---|---|
| 1 | Kiluth Tasks is the system of record for work, approvals, and handoffs. |
| 2 | Sign-off checkpoints freeze each artifact before the next unit starts — so downstream never builds on a moving base. |
| 3 | Pay-first at every money checkpoint: deposit before kickoff, hosting before go-live, maintenance before the period. |
| 4 | Finance is the source of truth for payment; everything is booked in ERPNext. |
| 5 | ERPNext spine: Lead → Opportunity → Quotation → Sales Order → Sales Invoice → Project → Resource, plus the Document register for signed documents. |