I build software for philanthropy.
I'm Mark. I was Fluxx's first engineering hire, and since 2018 I've built more than 40 integrations connecting grants systems to the finance, e-signature and productivity tools foundations run on. Now I'm building what comes next: grants data you can ask a question of, and systems that act on the answer.
- Fluxx integrations built
- 40+
- building and extending Fluxx
- 16 yrs
- building software
- 30+ yrs
Fluxx Preferred Partner · Workato Partner · Neo4j Certified Professional
What I do
Work directly with the senior architect who designs and builds it. No account managers, no hand-offs.
Integrations and automations
Your grants system connected to finance, e-signature, Microsoft 365, Google Workspace and Slack, so staff stop re-keying data.
Discovery, then a fixed-scope build
Custom software
Multi-tenant SaaS platforms, internal tools and APIs, designed from the data model up, with security enforced by the database.
Founding builder or fractional CTO
AI-native builds
Plain-language access to your grants data, agents that act with your approval, and knowledge graphs over your grant history.
Building MCP servers since April 2025
API and AI advice
An expert on call while your team builds: API guidance, data design, and AI on your grants data.
A prepaid bucket of hours
Connected across the whole grantmaking lifecycle
Each stage of grantmaking can run on a different system. I helped build the grants platform at the center from its early years, and I connect it to the tools you already use.
Across it all: AI and data
Your grants system joins the rest of your tools as one connected set, so you can ask questions and take action across all of it, through MCP servers, knowledge graphs and AI-native products.
Agreements
Connected Adobe Sign, OneSpan and DocuSign, so agreements send and file themselves
Payments
Connected banks, ERPs and Bill.com, including payments at national scale
At the center
Your grants system
Applications, reviews and awards. As Fluxx's first engineering hire, my work touched nearly every layer of the platform.
Impact
Helped build one of the first impact measurement platforms for funders
Communication
Connected Gmail, Outlook, Slack and Constant Contact, so updates and outreach reach the right people
Sound familiar?
Anything done by hand: downloading from one system, uploading to another.
At a national health nonprofit, that was six manual steps for every grant agreement. Now it's one status change. Their team estimated the streamlined agreement process saves hundreds of thousands of dollars in staff time. And signer details come straight from the grant record, so there are no copy-and-paste typos.
Before: 6 manual steps per agreement
- Download the agreement from the grants system
- Upload it to the e-signature system
- Copy and paste each signer's email
- Send it, then wait
- Download the signed copy
- Upload it back to the grants system
After: 1 step
Change the status in the grants system. Done.
Automate the repetitive work. Keep people in the decisions.
Systems I've connected
- Grants management
- Finance and ERP
- Payments and banking
- E-signature
- CRM and outreach
- Email and files
- Maps and location
- AI and data
Dynamics 365 Business Central
Constant Contact
Microsoft Dynamics 365 CRM
SS&C GoWire
currencylayer
Gmail
Outlook
SharePoint
Google Maps
OpenStreetMap
We build on the integration platform your team already uses, whether that's Workato, Power Automate or Zapier, or use custom code when none of them fits.
What's next
From connected to conversational
Integrations do the same thing every time, and they should: payments and signatures need to be exact. What's new is being able to explore your grants data in plain language, and start the right process when you're ready.
Which of our grantee organizations are registered in SAM.gov, and which registrations expire in the next 90 days?
I matched your grantee organizations to SAM.gov by their UEI. 38 are registered; these 2 expire in the next 90 days.
| Organization | Active grants | SAM.gov registration |
|---|---|---|
| Harbor Literacy Project | 3 | Expires in 41 days |
| Northside Food Collective | 1 | Expires in 73 days |
Your grants system and a public dataset, joined in one question. No report had to be built first.
Step 1
Connect
End the download-and-upload. Data moves between your grants system and the tools around it when something happens.
Step 2
Run the whole process
Sequencing, branching, documents and results coming back. A payment flow into your ERP, or e-signature end to end.
Step 3
Ask and act
Explore your grants data, and everything connected to it, in plain language. When something needs to happen, you approve it, and it runs through the integrations you trust. Your data stays governed.
Fixed steps for what must be exact. Conversation for everything you want to explore.
Not here for an integration?
Where is your team losing time?
Let's talk it through. Here's how we'd work together.
- 1 · FreeTalk it throughA free 30-minute call. We walk your process through six questions and size what discovery would take.
- 2 · Bucket of hoursIntegration discoveryTogether we map your systems, triggers and data flows into an integration design document. It's yours. Then you choose who builds the integration: me, your team, or another partner.
- 3 · Fixed scopeBuild and go liveThe design becomes a fixed-scope build. We test in your test environment, go live together, and I stay available after launch.
The call starts with six questions. In discovery, their answers become the design.
- What business process or problem will this solve?
- What data has to move: organizations, payments, documents?
- What triggers the move: a status change, a button, a schedule?
- One-way push or bi-directional?
- Does the other system have an API, and a connector on the platform you own?
- What comes back, and what should your grants system do when it does?