Consultation intake
Requests submitted through TempershiftLabs.com flow into a desktop lead queue where the request can be reviewed and converted into a client workspace.
A local-first desktop workspace that connects the practical side of client work: consultation intake, client records, project setup, billing, invoices, communication, mobile testing, deployment, and handoff.
WHY IT EXISTS
Leads, requirements, client history, scope, project files, communication, invoices, deployment steps, and support context often live in completely different tools. ClientForge was built to keep that operational context connected without turning the workflow into another generic CRM.
FROM FIRST CONTACT TO DELIVERY
Requests submitted through TempershiftLabs.com flow into a desktop lead queue where the request can be reviewed and converted into a client workspace.
Contact, project, package, files, working context, and client history stay tied to one durable local workspace.
Approved work can be translated into an organized project structure, technology decision, build prompt, and verification checklist.
Permanent sequential invoice IDs, retained client snapshots, line-item catalog, balances, status, archive/restore, and public lookup.
Gmail-sidecar workflows keep client-facing communication closer to the project context instead of treating email as a separate universe.
Expo staging, Android tooling, APK import, photo-mission workflows, project diagnostics, and deployment steps can live beside the client project.
ENGINEERING CHOICES
ClientForge treats important operational history as durable state. Invoices retain client snapshots rather than depending on whatever the client record says months later. Archive actions preserve data instead of deleting it. Public billing lookup is separated from private local ClientForge records through a sanitized server-side billing record.
MOBILE LAB
The same workspace can stage an Expo application, surface project readiness, import an APK, preview a mobile build, and keep native-device verification separate from visual staging.
CURRENT DIRECTION
New features are added against real operational needs and tested in the same environment used to manage Tempershift Labs projects.