LEAST Software operates as a principal consultancy. There is no account management layer, no delivery team behind a sales team, and no differentiation between who you speak to and who builds the system. Every engagement is led and delivered by Philip Lacey.
Principal Consultant
Philip Lacey
Founder, LEAST Software
Philip Lacey has designed, built, and operated software systems for over a decade. His primary reference work is the LEAST Software platform: a production enterprise system comprising eight integrated modules — workflow automation, analytics, content management, AI enrichment, systems integration, team management, compliance infrastructure, and communications. Every line of it is his direct work.
He has operated this system continuously in a production environment, which means his technical recommendations are grounded in what holds up under real operational load, not what reads well in a proposal. When he advises on architecture, integration, or database design, it is because he has built those systems and maintained them through scale, compliance audits, and changing requirements.
His consulting work covers the full stack: application design, database architecture, systems integration, AI implementation, security and compliance, workflow automation, and technical training. He engages at all levels — from a one-day architecture review to a multi-year platform build.
Technical Capability
Full-stack web applications, internal operational platforms, admin systems, workflow engines, multi-tenant architectures. PHP, JavaScript, SQL, REST APIs.
Relational database design, query optimisation, reporting systems, API integration, SAML 2.0, LTI 1.3, OAuth, SCORM, xAPI, HRIS and identity provider connections.
LLM integration with human-in-the-loop governance, content enrichment pipelines, intelligent classification, workflow automation, cron and event-driven processing.
ISO 27001 ISMS implementation, GDPR data lifecycle management, TOTP MFA, parameterised SQL, static analysis gates, full audit trails, IP allowlisting.
How engagements work
Every engagement begins with a direct conversation about the operational challenge. No obligation, no pitch. The aim is to understand what is actually needed before any proposal is made.
Requirements are documented clearly before development begins. Architecture choices are explained in terms of what they mean for the operation, not just what they mean technically.
Systems are built to production standard, tested thoroughly, and handed over with documentation and training. The engagement ends when the organisation can operate what has been built independently.