I build on the systems your team already operates in. CRMs, doc tools, accounting, comms, scheduling, AI - listed below by where they sit in the workflow.
I do not pick tools for novelty. I pick the one already in use, or the closest mature alternative if there is a real gap.
CRM & Sales
Where deals and pipeline live.
HubSpot
Pipedrive
Salesforce
Attio
Close
Copper
Folk
Airtable
Enrichment & Intelligence
Where lead context comes from.
Apollo
Clearbit
ZoomInfo
LinkedIn Sales Navigator
Lusha
Hunter
Communications
Where conversations actually happen.
Slack
Microsoft Teams
Gmail
Outlook
Front
Intercom
Scheduling & Calendar
Where time gets committed.
Calendly
Cal.com
Google Calendar
Outlook Calendar
Chili Piper
Documents & Storage
Where paperwork lives.
DocuSign
HelloSign
PandaDoc
Google Drive
Dropbox
Box
OneDrive
Project & Knowledge
Where work gets tracked.
Notion
ClickUp
Asana
Linear
Monday
Trello
Coda
Finance & Billing
Where money moves.
Stripe
QuickBooks
Xero
NetSuite
Plaid
Ramp
Brex
AI & Extraction
Where unstructured becomes structured.
OpenAI
Anthropic
Google Gemini
Document AI
Mistral
Glue & Infrastructure
Where everything else gets wired.
Postgres
Supabase
Retool
Custom APIs
Webhooks
+ custom APIs, internal databases, and whatever your firm runs on.
Stack philosophy
Three rules I hold the stack to.
01
No proprietary platform
I never make my own tool a dependency. Every build lives on infrastructure your team can swap if you have to.
02
Migrate as a choice, not a prerequisite
If a tool is genuinely blocking your workflow I say so. Otherwise I build on top of what you already pay for.
03
Boring tech where it counts
Postgres, well-known APIs, mature SDKs. Novelty does not survive 18 months. Documented stability does.
Build on your stack
Pick a workflow, keep your tools.
6 service categories, all built on top of the systems your team already pays for. Send one task that is bleeding hours; I send back a written audit within a business day.