Open source & give back
We give away the tools we built to run our own shop.
Not demos, not lead-magnet PDFs. The actual tools, MIT licensed, source included. We publish them because the versions of these that already existed were either locked behind a subscription or did not exist at all, and that cost us weeks we would rather you keep.
What you get, and what it actually does
Every one of these came out of a real job. Nothing here was built to be a giveaway.
Contrast Checker
One click outlines every piece of text on the page that fails WCAG contrast, and lists the exact ratios.
Bookmarklet · MIT
AI Studio Export
Export a complete HighLevel AI Studio project as a ZIP, or push it into a GitHub repository you control.
Browser tool · MIT
GHL Theme Starter
Two themes and two icon packs for the HighLevel sidebar. Pick, copy, paste.
One HTML file · MIT
HighLevel CSS Cookbook
Twenty-two copy-paste CSS recipes for HighLevel: sidebar, menu labels, login page.
Markdown · MIT
Agent Skills Pack
Six skills and two output styles for Claude Code and Codex, the ones we run on our own repos.
Skill files · MIT
What we mean by giving it away
Open source gets used as a marketing word. Here is the version we actually hold ourselves to.
We publish the thing, not a teaser
Every tool here is the real one, MIT licensed, with the source in one readable file wherever we can manage it. No feature held back for a paid tier, no watermark, no sign-up wall on the code itself.
We credit the people we borrowed from
Where a tool builds on someone else's open-source work, their licence and copyright travel with it, and each derived file names its upstream and the exact commit we took it from. Taking freely and saying nothing is not open source, it is just taking.
We ship what the mistake taught us
The cookbook keeps the two selectors that broke our own contract builder. The checker exists because we could not see our own contrast failures. Publishing the fix without the failure would make us look better and help you less.
Use it commercially, owe us nothing
MIT, on all of it. Put it in client work, put it in your own product, charge for the result. All the licence asks is that the copyright line stays with the code, and every file already carries it for you. Nothing is required in your own product. If it saves you a day, that is the whole return we were after.
We needed it, so we built it. Then everyone asked for it.
iBluSend was an internal tool before it was a product. We were running an agency on HighLevel and losing conversations to SMS that nobody opened. What we wanted was real iMessage, blue bubbles, sent from a real device, syncing both ways with the CRM we already lived in. Nothing on the market did that, so we built it for ourselves.
Then clients saw it. Then their friends asked. The demand got loud enough that we turned an internal system into a product anyone can buy, and it has kept growing into the most capable messaging platform we know of for teams running a CRM: native integrations rather than webhook glue, no carrier registration to wait on, and no per-message fee.
That is the whole pattern of how we work. We build the system, we run it in anger on our own business, and only when it survives that do we hand it to anyone else. The free tools further up this page came out of the same workshop.
Blue bubbles
Real iMessage, not green-bubble SMS
No A2P
No carrier registration, no campaign approval
$0
Per-message fees, sending from your own device
Two-way
Replies sync straight back into your CRM
Native integrations
Built for us.
Proven on us.
Then given away.
Colorado · est. 2022
Take the tools. Keep the change.
Everything above is free and stays free. If you would rather we built the system instead of you, that is the other half of what we do.