25% → 85%
contact-rate improvement
Reported result from an earlier operations-redesign engagement, where process, ownership, and follow-up changed together.
Experience
Operations taught me what software delivery can forget.
My career did not begin in software. It began in operations—where broken handoffs, weak controls, missing procedures, and unclear ownership have immediate business consequences. That operating background is why I manage technical delivery differently today.
Career story
Three eras, one throughline.
I have spent more than fifteen years making execution more controlled, measurable, and understandable—first through operations, then through digital systems, and now across technical delivery and AI-assisted products.
Operations foundations
The early work was close to the consequences: collections, contracts, procedures, bids, KPIs, service levels, administration, and the handoffs that determine whether a business performs.
Selected roles and engagements
- Olivieri — Project Manager & Administrative Coordinator
- Grunalco — Operations Manager / Administrative Director
- A.C. Asesores — Project Manager & Strategic Management Consultant
What compounded
- SOP and control design
- KPI and OKR operating rhythms
- Commercial, collections, and service operations
- ERP and operational transformation
- Executive and cross-functional decision support
Digital transformation and systems
Operational knowledge became system design: lifecycle models, role-based views, CRM and ERP-lite structures, automation, governance, and adoption.
Selected roles and engagements
- Victus Global — Systems Designer — No-Code, Automation & AI Workflows
- Jane’s Weather — Agile Software Business Analyst / Delivery Lead
- General Development — Project Manager / Operations Lead (Contract)
What compounded
- CRM and ERP-lite architecture
- Requirements and Gherkin acceptance criteria
- UAT, QA visibility, and release readiness
- API and delivery documentation
- Remote cross-functional coordination
Technical delivery, automation, and AI-assisted products
The current practice sits between business and engineering: source-of-truth decisions, integration boundaries, technical delivery, product operations, AI-assisted implementation, and evidence-led acceptance.
Selected roles and engagements
- TH3RD GROUP — Product Operations & Automation Lead
- FastVideo — Technical Project Manager · Product Operations Lead · Systems Architect
- Caul Group / Sympli Mortgage — Integration Architect · Technical Product Owner · Operations Automation Lead
What compounded
- Integration and source-of-truth architecture
- AI product and implementation direction
- CRM-to-delivery operating models
- Automation cost and exception design
- Environment, release, rollback, and reconciliation judgment
Earlier operations impact
Systems thinking before software.
These figures are reported engagement results from approved career source material. They are included with their operating context and are not generalized promises.
5 → 2 days
pre-legal response time
Reported result from an earlier operations engagement after controls and handoffs were redesigned.
12 → 7 days
legal-start cycle
Reported result from an earlier operations engagement, presented as cycle-time context rather than a universal benchmark.
Current position
Technical Project Manager & Delivery Systems Architect
Today, I connect business goals, CRM, product delivery, automation, documentation, quality controls, and reporting so technical and operational teams can move with clarity and control.
The thread has remained consistent: understand the real system, define who and what owns truth, create executable controls, and make the result visible enough to improve.