Leads, qualification, follow-ups, customer conversion and pipeline activity.
The Current Family
One operating architecture. Multiple service platforms.
The Current Family is the product ecosystem from soucy.company. Shared operating engines power specialized platforms for different service industries, allowing each product to speak the language of its market without rebuilding the foundation underneath it.
Shared operating foundation
CurrentCore
CurrentCore coordinates company context, records, workflows and cross-engine state. It is the foundation that lets each Current platform reuse the same operating architecture while adapting terminology and workflows for its industry.
↓ shared context · shared records · shared orchestration ↓
Current engine architecture
Specialized engines. Shared across the family.
Each engine has a defined role. The platforms determine how that capability is expressed for a specific industry.
Pricing, line items, proposals, approvals, deposits and conversion into work.
Jobs, work orders, tasks, checklists, logs, files, photos, materials and costing.
Calendars, bookings, appointments, crews, resources and conflict management.
Staff, roles, teams, timekeeping, attendance, onboarding and time off.
Expenses, recurring costs, budgets, credits and operational financial data.
Invoices, balances, billing states and completed-work billing handoffs.
Online payments, receipts, refunds, reconciliation and payout state.
Moves operational context and events between engines automatically.
Assignments, alerts, approvals, reminders and operational attention.
Dashboards, KPIs, workload, receivables, trends and operational visibility.
Roles, permissions, company isolation, row-level controls and trust boundaries.
Customer-facing estimates, work information, invoices and payment access.
Templates, documents, files, photos and reusable business content.
Maintenance plans, recurring visits, schedules and recurring billing handoffs.
Coordinates the shared company context and cross-engine operating state.
Service platforms
Built for different industries. Powered by the same family.
Only BuildCurrent is currently live. The additional platforms below are future Current Family products and are clearly marked Coming Soon until active development begins.
BuildCurrent
Contractor operations.
For contractors, trades, construction and property-service operators. Lead → Estimate → Job → Schedule → Crew → Invoice → Payment.
Explore BuildCurrentServiceCurrent
Service-business operations.
Planned for cleaning, recurring service, repair, inspection, maintenance and other appointment-driven service businesses.
Not yet in active development.PropertyCurrent
Property & facility operations.
Planned for property managers, building operators, facilities teams and recurring maintenance environments.
Not yet in active development.FleetCurrent
Mobile field & equipment operations.
Planned for mobile technicians, equipment service, repair fleets and asset-centred field operations.
Not yet in active development.How the family integrates
Same engine. Different vertical expression.
The underlying engine stays consistent while each service platform adapts its language and workflow to the industry it serves.
| Engine | BuildCurrent | ServiceCurrent | PropertyCurrent | FleetCurrent |
|---|---|---|---|---|
| QuoteForge | Construction estimate | Service quote | Work authorization / proposal | Repair estimate |
| FieldCurrent | Projects & jobs | Service orders | Work orders | Equipment service jobs |
| TimeGrid | Crew schedule | Appointments | Maintenance schedule | Technician dispatch |
| Cycle | Recurring maintenance | Recurring visits | Preventative maintenance | Service intervals |
| Bridge | Customer portal | Client access | Tenant / owner access | Service customer access |
| Pulse | Job & financial KPIs | Service performance | Property performance | Fleet & service performance |
Shared data philosophyEnter information once. Carry it forward.
A customer should not be recreated for a quote. A quote should not be rebuilt when it becomes work. A schedule should not require re-entering the work that already exists. Billing, payment and reporting should continue from the same operating history.
That principle is what turns the Current engine family from branding into architecture.
Where we are today
BuildCurrent proves the architecture first.
The Current Family grows only as the shared foundation proves reusable. Future platforms will move from Coming Soon to active development when their build begins.