Three senior builders. No junior handoff.
You work directly with the people who scope and build the work — an operator, an integration engineer, and an infrastructure architect. No revolving bench of juniors.
Daniel Speiss
Founder · Operator & Revenue Systems Architect
Daniel owns the operating and revenue layer at OpsPal — the work a fractional COO or RevOps lead would carry, scoped to what the business actually needs. He maps how a business actually works — where revenue gets stuck, what the owner needs to stop carrying, what the team should own, and which systems to build first. His background spans sales floors, sales enablement, RevOps, underwriting operations, CRM architecture, AI-assisted systems, and finance-business operations, including co-founding BH Capital Funding. He architects the systems and integrations from the business-logic side and leads scoping and delivery end to end. Through Kinaura by PRISM Dynamics he also brings a people-systems lens: role fit, team cohesion, and whether the right people own the right work.
RevOps · sales operations · sales enablement · underwriting operations · CRM & business-logic architecture · AI workflow design · API/integration architecture · owner offload & delegation · people systems · operating cadence · roadmapping
Josh DiGiorgio
Infrastructure & Product Architect
Josh owns the infrastructure foundation and product architecture. He holds an MS in Systems Engineering from George Washington University and has seven years shipping complex software in regulated, performance-sensitive environments — including Fortune 500-scale programs and quantitative-trading infrastructure. He designs the deployment foundations OpsPal's builds and products run on.
FastAPI · Supabase · Railway · Cloudflare · Docker · product architecture
Tal Weiss
Backend Engineer & Salesforce / Integration Specialist
Tal builds the systems and the integration layer most studios skip — Salesforce Apex, SOQL, and Flows; AWS Lambda and Step Functions; webhooks, OAuth, and Stripe; NestJS/Express on Postgres and MongoDB. He works sandbox → staging → production with documented handoff, so what ships is reliable and maintainable. He's the person who makes systems actually talk to each other.
Salesforce (Apex/SOQL/Flows) · AWS Lambda · Step Functions · webhooks/OAuth · NestJS/Express · Postgres/MongoDB
Capability matrix
Who leads what. Every engagement draws on all three.
| Capability | Daniel | Tal | Josh |
|---|---|---|---|
| Strategy & operations | Lead | — | — |
| RevOps & CRM | Lead | ✓ | ✓ |
| Salesforce (Apex/SOQL) | ✓ | Lead | — |
| Backend & APIs | — | Lead | ✓ |
| Cloud automation (AWS) | — | Lead | ✓ |
| Infrastructure & architecture | — | ✓ | Lead |
| Integrations (OAuth/webhooks/Stripe) | — | Lead | ✓ |
| Product & app build | ✓ | ✓ | Lead |
| Delivery & handoff | Lead | ✓ | ✓ |
How the team works together
One small team, four phases, clear ownership.
Daniel finds the bottleneck
Business logic, operator reality, RevOps, and delivery — from first call to handoff.
Tal wires the systems
CRM, backend, and integration logic — the layer that makes systems talk to each other.
Josh builds the foundation
Infrastructure and product architecture that holds up under real load.
Together, the backbone
Diagnose → Architect → Build → Run, with the same senior people the whole way.