DebugInit
Build only what your operations need.
Start with reusable Business Foundations, then configure workflows, data, roles, policies and intelligence around your organisation.
One platform. Twelve Business Foundations. Shared identity, workflow, data, audit and AI.
Foundation philosophy
A Business Foundation is a reusable operational base, not a rigid finished product. It provides the records, workflows, controls and reports commonly required for a business function, and is then configured around the processes, terminology, policies and operating model that are specific to your organisation.
That is the difference between DebugInit and a conventional software suite: you introduce only the Business Foundations your operation needs, in the order it needs them. Foundations that are not required do not add implementation complexity or licensing cost.
The foundation map
Twelve Business Foundations covering the core functions most organisations operate. Start with the ones your organisation needs today and add others as operations evolve.
CRM & Revenue
Lead capture, routing, account structures, opportunities, activities, proposals, renewals, customer health, forecasting and revenue analytics.
Projects & Work Management
Projects, portfolios, tasks, sprints, capacity, dependencies, timesheets, risks, decisions, documents and operational work queues.
People, HR & Payroll
Employee records, organization structure, hiring, onboarding, attendance, leave, performance, payroll workflows and employee service.
Finance & Accounting
General ledger, receivables, payables, expenses, budgets, assets, tax workflows, reconciliations and management reporting.
Inventory & Warehouse
Items, variants, lots, serials, locations, movements, reservations, counting, fulfilment, returns and planning.
Procurement & Vendors
Purchase requests, approvals, sourcing, vendor onboarding, contracts, purchase orders, receipts, invoice matching and performance.
Support & Service
Cases, tickets, queues, SLAs, knowledge, triage, field service, quality, customer communication and service analytics.
Documents & Knowledge
Documents, records, policies, SOPs, templates, approvals, retention, enterprise search and AI-assisted understanding.
Editorial & Publishing
Story planning, assignments, writing, review, approval, scheduling, corrections, releases, analytics and audit.
Marketing Operations
Campaigns, briefs, calendars, assets, approvals, audiences, channel execution, performance and AI-assisted content operations.
Assets, Facilities & IoT
Asset registers, locations, maintenance, inspections, facilities requests, sensors, alerts, work orders and lifecycle analytics.
Executive Analytics
Cross-functional KPIs, operational health, exceptions, forecasts, scenario views, automated narratives and action tracking.
Cross-foundation workflows
The greatest value rarely exists inside one Business Foundation. It comes from processes that move across several foundations without requiring duplicate entry, disconnected approvals or manual handoffs.
Quote to cash
An opportunity becomes a proposal, an approval, an order, a delivery and an invoice without being retyped at any step.
Hire to retire
A role request moves through approval, onboarding, access, payroll and equipment as one process rather than five checklists.
Procure to pay
A request finds a vendor, gets approved against a budget, arrives in inventory and reconciles against the invoice.
Issue to resolution
A customer problem reaches the person who can fix it, carrying the account, the history and the entitlement with it.
Shared foundation services
Every Business Foundation runs on the same shared platform services. Identity, workflow, audit, integration, data controls and AI are implemented once and reused as additional foundations are introduced.
One identity model
A person, a role and a permission mean the same thing in every foundation. Access reviews stop being twelve separate exercises.
One workflow engine
Approvals and escalations behave consistently, so a rule learned in one foundation is not relearned in the next.
One audit trail
Cross-foundation processes produce a single readable history rather than fragments in four systems.
One AI layer
Copilots and extraction share the same grounding, permissions and evaluation wherever they appear.
Foundation implementation model
Four working rules that decide whether a Business Foundation programme compounds or sprawls.
- 01
Start with one foundation
Begin with the Business Foundation covering the process that creates the greatest cost, risk, delay or operational friction — not simply the one that is easiest to demonstrate.
- 02
Configure, do not fork
Fields, workflows, roles, policies, forms, dashboards and terminology are configured within the Business Foundation rather than creating a separate codebase for every customer.
- 03
Connect what remains
Existing systems that continue to provide operational or economic value are integrated with the relevant Business Foundations rather than replaced without justification.
- 04
Add the next foundation
Each additional Business Foundation reuses the identity, workflow, audit, data and integration services already established, reducing the cost and complexity of expansion.
Foundation ownership model
What your organisation controls within each Business Foundation and across the shared platform.
- Your data
- You retain rights to the business data used across every Business Foundation, subject to the export, retention and transition terms defined in the agreement.
- Your configuration
- Workflows, fields, roles, forms, policies, dashboards and terminology configured within each Business Foundation remain visible and manageable rather than becoming undisclosed vendor logic.
- Your deployment
- The environment in which each Business Foundation operates is selected as part of the assessment and confirmed in the deployment agreement.
- Your exit
- Data export, configuration handover and transition procedures are defined for each deployed Business Foundation before implementation rather than negotiated only when the relationship ends.
Specific terms vary by deployment and customisation model and are set contractually. This page describes the position, not the contract.
Design your Business Foundations
Bring one process that crosses two or three operational areas. We will map the Business Foundations, shared services, integrations and controls required to run it as one connected system.