Service · Enterprise Integrations & Identity
Integrations that hold: OAuth, SSO, webhooks, and APIs that don’t fall over.
Integrations are where SaaS products quietly fail: tokens expire mid-workflow, webhooks double-fire, a third-party API rate-limits you at the worst moment, and the enterprise deal stalls on SSO. I build this layer daily at Writer — OAuth-based knowledge connectors and SSO/SCIM/IdP provisioning — and I’ve built platform integrations across products like Slack, Jira, and GitHub-class ecosystems.
Sound familiar?
The situations this service exists for.
- ■Enterprise deals stall on SSO, SCIM, or IdP requirements your product doesn’t meet yet
- ■OAuth connectors work in demos and break in production: expiry, revocation, scope drift
- ■Webhooks fire twice, arrive out of order, or vanish — and your data quietly diverges
- ■Every third-party API outage becomes your product’s outage
Scope
What the work covers.
- ■OAuth 2.0 connector design: token lifecycle, refresh, revocation, scope hygiene
- ■Enterprise identity: SSO, SCIM provisioning and deprovisioning, IdP integration
- ■Webhook architecture: idempotency, ordering, retries, dead-letter handling
- ■Third-party API resilience: rate-limit strategy, backoff, circuit breaking
- ■Data mapping and conflict resolution across systems of record
- ■Integration observability so failures surface before customers report them
Outcomes
What you end up with.
- ■Connectors that survive token expiry, revocation, and the security questionnaire
- ■Identity flows that unblock enterprise deals instead of stalling them
- ■Integrations that degrade gracefully when the other side misbehaves
Engagement formats
How to buy this.
Technical Strategy Session
60–90 minutes
A paid working session on one defined problem: an architecture choice, an AI feature plan, a performance question, a build-vs-buy call. You bring the context; I bring pattern recognition from 13+ years of shipping in situations like yours.
Start here →Product & Architecture Diagnostic
3–5 days
A focused investigation of one high-impact problem. I read the code, profile the system, interview the people closest to the pain, and separate symptoms from causes.
Start here →Implementation or Rescue Sprint
2–4 weeks, fixed scope
I take hands-on ownership of the most critical part of the work — writing production code, making the blocking decisions, and coordinating with your product, design, and backend people until it ships.
Start here →Fractional Staff Engineer / Technical Advisor
Monthly engagement
Ongoing senior ownership at a defined weekly cadence: architecture reviews, product-engineering alignment, technical mentoring, and selective hands-on delivery where it moves the needle most.
Start here →Writer
AI agents demo well and fail quietly. At Writer I build the layer that makes them dependable: workflow structure, grounded knowledge, enterprise identity, and the unhappy paths.
LottieFiles
Every plugin host has its own sandbox, auth constraints, and review process. I helped LottieFiles ship one coherent toolchain across Figma, Adobe, Canva, VS Code, WordPress, and more.
Tell me what is blocked, underperforming, or difficult to ship.
I will tell you whether I can help — and what the smallest useful next step would be. If I’m not the right person, I’ll say so.