Custom platforms where everyone sees their part
I build platforms for small operations where work passes through several hands. Admins, staff and clients each get their own dashboard: they see what they should see, and they can do what their role allows and nothing more. It's the back office of a small operation, in software, built around how your work actually moves.
Get startedIs this you?
- Work moves from person to person by email, and something is always sitting in someone's inbox.
- One person knows where everything stands, and it's usually you.
- The spreadsheet has columns some people shouldn't see, so you keep several versions of it.
- Approvals wait until someone chases them.
- The same details get typed into three places, and one of them is always out of date.
- You bought a product that does most of it, and the part it doesn't do is where your week goes.
What I build
Everything below runs in CDAFlow today.
A dashboard for each role
Admins, brokers and agents each get their own view, with the permissions and data for their role. Rising Tides and ScheduleGroups do the same for admins, supervisors and participants.
Invitations and onboarding
People are invited in, set up from day one, and you can see who's still getting started.
Details pulled from documents
AI reads an uploaded contract and pulls out the address, price, parties and dates, so nobody retypes them.
Checklists that know the rules
AI sorts each uploaded document against the checklist for that state and deal type, so everyone can see what's still missing.
Calculations done up front
Commission plans (split, cap or flat fee) are worked out the moment a deal is created, not in a spreadsheet afterwards.
One review queue
Everything waiting for approval lands in one place, and the person who approves it does so in one click.
Paperwork generated, signed and sent
The commission disbursement authorization (CDA) is built from the deal, e-signed and emailed to the title company.
Several offices, one system
A brokerage with more than one office runs them all on the same platform.
Each organisation on its own
Every brokerage is a separate tenant, with its own logo, colours, people and deals, and its data kept apart from every other brokerage's.
The platform I run
CDAFlow: software I built for real estate brokerages
CDAFlow is back-office software for real estate brokerages, and it's a product I run. I'm not a broker; brokerages are my customers. I built the platform and its website, and I maintain both. Two brokerages, one in Texas and one in Colorado, run their transactions on it today, each as its own tenant with its own branding. A deal moves from intake to compliance to commission to disbursement, and each person involved sees only their part of it.
It took about four months, and it's the most extensive thing I've built. I knew none of it when I started. Before I could make anything useful, I had to understand how a brokerage actually moves a deal. Learning the workflow first is the part of the job I'd do for you too, whatever your field.
"CDAFlow completely changed how we handle transactions in our brokerage. What used to take hours of back-and-forth spreadsheets is now done in minutes."
If you run a brokerage, CDAFlow itself is what you're looking for.
Visit www.cdaflow.comThe same idea in coaching supervision
Rising Tides and ScheduleGroups give admins, supervisors and participants each their own dashboard. ScheduleGroups runs a volunteer supervision program with more than 150 participants, 20+ facilitators and 3 admins.
More on scheduling platformsA product, a no-code tool, or a custom build?
If a product exists for your industry and your process is standard, use it. Most industries have a few; real estate brokerages have several, CDAFlow among them. No-code builders such as Softr and Knack let you put a simple portal on top of your own data yourself. They're a good way to test an idea.
A custom platform starts to make sense when:
- the way work moves through your operation is part of what sets you apart
- you keep exporting to a spreadsheet to finish what the tool should do
- you need several roles, with rules about who sees and approves what, that no product lets you set
- documents have to come out of the system generated, signed and sent
- each tool you've tried covers part of the job, and you're the glue between them
How I work
We talk about the problem
Not features. What's actually taking your time, where things go missing, what you're working around.
I map the workflow
Then I show you what I've understood, because that's where most projects go wrong.
I build in the open
You see it early and you see it often, and it changes as you use it.
It goes live
And I'm still here when the next thing comes up.
Questions people ask
- How long does it take?
- It depends on how many roles and rules there are. CDAFlow took about four months. A smaller platform starts with one role and one workflow, goes live, and grows in small steps.
- What does it cost?
- It depends on the number of roles, the rules between them, the documents involved and what it connects to. We talk it through and agree on a price that fits what you actually need.
- Do I need to explain it in software terms?
- No. You tell me how the work moves today, and I learn it before I build anything. When I started CDAFlow, I knew nothing about brokerage commissions.
- Can it start small?
- Yes. Most platforms start with the one workflow that hurts most, and grow from there.
- What if we need changes later?
- I'm still here. Most platforms grow in small steps after launch, and I work that way on purpose.
- Does it work on phones?
- It's built to adjust to phones and tablets as well as desktops.
Tell me how work moves through your operation
Who hands what to whom, where it waits, and what only you know. I'll tell you honestly whether a platform helps, or whether a product you can buy will do.
Get started