Our Work
Built To Be Inspected.
What we build and how we build it — Salesforce development, lead-to-cash automation, security hardening, compliance posture scanning, and the AWS architecture that ties them together. Where the code is public, the link goes straight to the repository.
Engagement-to-Invoice Billing Engine
A working Salesforce package for consulting operations: engagements, time entries, milestones and invoices modelled as first-class objects, with invoice calculation in Apex and the review surfaces built as Lightning Web Components. The source is public — read the tests, not just the pitch.
Lead-to-Cash Pipeline Automation
The path from a booked discovery call to an activated engagement, built as Salesforce metadata rather than as tribal knowledge. Qualification, conversion and the contractual gates that follow are enforced by record types, validation rules and permission sets — so the process holds when nobody is watching it.
Security Architecture & Control Hardening
Infrastructure built and hardened against SOC 2 and ISO 27001 control expectations, and gap analysis that maps findings to named controls instead of a generic checklist. Readiness work is scoped to what an auditor will actually ask for.
Compliance Posture Scanning for Healthcare
Posture scanning built for environments where the data is the liability. The scanner reads configuration state and receives no PHI at all, and what it reports is configuration state — whether that state amounts to a breach is a determination that belongs to the covered entity, never to a vendor tool.
AWS Integration Middleware
The seam between a public website and a system of record, built so the browser never holds a credential it should not have. API routes run in Lambda behind API Gateway, containers run on ECS Fargate in private subnets, and every secret is fetched at runtime rather than baked into an image.
AI Sales Agent on Salesforce
An AI SDR that works the top of the pipeline and writes what it learns back to Salesforce Leads. It reaches the CRM through the same server-side middleware as every other component — an agent gets no direct credential and no privileged path of its own.
Want this built for your team?
Tell us what you're trying to solve and we'll tell you how we'd approach it.
Want to know how we bill? View our pricing approach.