Bluefrog did not start with AI. We started with payment processing, real-time alerting, mobile platforms and business automation — systems that had to run correctly whether or not anyone was watching. Every one of those problems is the same problem we solve now: connecting software to the way a business actually operates.
The domains changed. The discipline never did — take messy real-world activity, move it through systems reliably, and give an operator something they can act on.
Payments came first. Money systems are unforgiving. Building technology for the GE CareCredit system, and later the initial kiosk-based platform for US Payments designed around PCI and NACHA requirements, meant secure transaction handling, settlement rules and back-office integration that had to reconcile every time. That work established the habits we still use: validate at the boundary, never trust a single source, and integrate with the systems of record rather than around them.
Then real time. In 2001 we built one of the early real-time mobile tornado alert systems in Oklahoma — ingesting live data, evaluating conditions automatically, and distributing alerts to mobile devices at scale, years before push notifications existed as a platform feature. That is an event-driven pipeline: watch a stream, decide what matters, notify the right person immediately. It is the identical shape as the alerting inside revenue intelligence today.
Then mobile, at platform scale. ICANN's first mobile website. Mobile technology and frameworks for property discovery and customer engagement at Lennar and Ryland Homes. Simpleview's initial mobile website platform — the system used to deploy mobile web experiences for hundreds of CVBs and Chambers of Commerce. And mobiManage, our own mobile platform company. Multi-tenant, configurable, extensible: the same architecture thinking behind the Bluefrog Intelligence Platform.
Then commerce, automation and information systems. Online ticketing, memberships, donations and back-office integration for the Tulsa Zoo. On-demand video streaming, subscriptions and e-commerce for Roger Raglin Outdoors. A substantial portion of BizIQ's internal technology infrastructure — CRM, management systems, workflow, operational tooling and marketing automation. Information platforms like the University of Tulsa Information Security Center, and recent custom community software such as Phoenix Elks #335. Read how that becomes Operational AI — or how we approach custom software now.
Described as engineering, not marketing. Filter by discipline — the categories overlap on purpose, because most of these systems did more than one job.
Built technology for the GE CareCredit system — financial and business technology operating inside a regulated consumer-credit environment, where correctness and auditability are the product.
The initial kiosk-based payment platform, designed around PCI and NACHA requirements: secure transaction processing, device-level handling and back-office integration. corp.uspayments.com →
One of the early real-time mobile tornado alert systems: live data ingestion, automated alert logic and mobile distribution at scale. Event-driven intelligence, built decades before the term.
Built ICANN's first mobile website — mobile delivery for the organization that coordinates the internet's namespace, under real content-governance constraints. icann.org →
Mobile technology and frameworks for property discovery and customer engagement at one of the nation's major homebuilders — inventory data rendered for handsets, not desktops. lennar.com →
Mobile technology and frameworks for property discovery and customer engagement for another major national homebuilder — the same engineering problem, a different data source.
Built Simpleview's initial mobile website platform — the system used to deploy mobile web experiences for hundreds of CVBs and Chambers of Commerce. Multi-tenant from day one.
Our own mobile platform and SaaS company. Journal Record "Innovator of the Year," 2009. Powered mobile sites across tourism, real estate, restaurants and universities.
Jeff Beasley founded Straxis, a Tulsa interactive technology company, and sold it in the 2000s. Straxis built mobile and interactive platforms for universities, cities and destination organizations.
Built the software behind U360 Mobile, a campus mobile platform for higher education. Another reusable, multi-tenant platform rather than a one-off build.
Named deployments included Park City, Boston, Bay Area Houston, Sonoma County, Tulsa and the Kensington & Chelsea Chamber in the UK. Mobile web deployments for tourism and destination organizations, published from a shared platform: templated delivery, per-tenant content, device-aware rendering.
Mobile experiences for university audiences — directories, schedules, campus information — delivered on the same multi-tenant platform architecture.
Property discovery on mobile: listing feeds normalized, search built for small screens, and agent-facing tools published from one platform instead of one build per brokerage.
Online platform and storefront: ticketing, memberships, donations, e-commerce and back-office integration for a high-traffic public attraction. tulsazoo.org →
On-demand video streaming combined with e-commerce and subscriptions — entitlement logic, recurring billing and catalog all in one platform. rogerraglin.com →
Built a substantial portion of BizIQ's internal technology infrastructure: automation, management systems, CRM technology, operational tools, workflow and marketing automation infrastructure — the internal machinery a company runs on.
Information platform for programs, faculty and research directories — content management and an accessible information architecture built for an academic research center.
A national faith-based directory platform: a searchable database of tens of thousands of ministries filterable by state and category, organization self-submission with review, resource routing for people seeking help, and Stripe-based donation handling. A data and search problem, not a brochure. ct3.org →
Custom PHP and Bootstrap community platform — events, member communication and publishing, built and maintained as a working system rather than a template. phx.elks.news →
Satellite-linked fleet management with real-time telemetry and command visibility — a distributed system built when availability, not features, was the requirement.
Encrypted medical data backup systems for healthcare organizations, plus the information security policies and standards written around them. Information security →
A veteran-owned direct mail platform we built and run ourselves — list handling, design, print and mail workflow, and campaign tracking connected back to response.
Product development and the commerce platform behind SnugSpin, a consumer hardware product with a patent pending. Evidence that the engineering habit extends past software.
A city-wide community and events platform — directory, listings and editorial publishing, built to keep a metro area informed. Covered by the Tulsa press at launch.
A sports content and scores platform — our earliest documented press coverage, from 2001, and an early example of building for an audience rather than a brochure.
Technology for a national real estate auction company — property data, bidder-facing experiences and the mobile access layer around a live transaction business.
Work delivered in the carrier ecosystem during the era when mobile web standards were still being written.
Mobile event experience for a large music festival — schedules, lineups and on-site information delivered to phones years before every event had an app.
Mobile experience for Oklahoma's innovation and entrepreneurship organization, whose summit series we also spoke at.
Mobile property search and agent tooling on the same multi-tenant platform architecture behind the rest of our real estate work.
Information architecture and publishing systems for a major philanthropic organization — complex content, many audiences, strict accessibility expectations.
A live Operational AI deployment for an HVAC, plumbing and electrical operation: AI Answer Hub publishing hundreds of categorized answers, call intelligence, and marketing data connected through to booked work. calltripleplay.com →
An Answer Hub of expert answers organized into topic categories with search, plus the lead and call intelligence layer underneath it. affordabledoorco.com →
A configurable, modular AI and business-intelligence platform connecting the systems a company already uses — voice, evaluation, revenue, marketing, customer and automation modules. Explore the platform →
Current work: call intelligence, rubric evaluation, CRM and field-service integration, revenue reporting and automated follow-up wired into live operations. ServiceTitan integration → · Custom APIs →
Historical work is described as engineering. For how current engagements are structured, see how we create efficiency.
Being early is not a personality trait. It is what happens when you keep asking the same question — what could this system do if the data actually moved?
Every era on this page looked speculative at the time. Sending automated severe-weather alerts to mobile phones in 2001 required convincing people that a phone was an alerting device. Building mobile websites before the smartphone was standard equipment meant arguing that the small screen was going to matter. Building CRM, workflow and marketing automation infrastructure meant explaining why software should do the coordination a person was doing by hand.
None of those were predictions about technology. They were observations about work — that a human being was doing something repetitive, or slow, or invisible, and that a system could do it continuously instead. That is exactly what Operational AI is. Generative AI creates things; Operational AI connects to the actual business, reads what is happening inside it, evaluates it against the company's own standards, and acts.
Which is why AI did not create our technology company. AI expanded what our technology can do. The integration layer, the data plumbing, the reconciliation logic, the multi-tenant delivery, the alerting pipeline — that was all built before the model showed up. The model made it far more useful. See how AI systems integration works or what happens to a single phone call once it is connected.
| Era | What we built | What it's called now |
|---|---|---|
| Payments | Kiosk transaction platform built to PCI & NACHA requirements | Embedded payments |
| 2001 | Automated real-time mobile weather alerting | Event streaming · push |
| Mobile | Mobile web frameworks before smartphones were default | Mobile-first |
| Platform | Multi-tenant publishing for thousands of organizations | SaaS |
| Commerce | Ticketing, memberships, subscriptions, streaming | Digital commerce |
| Automation | CRM, workflow & marketing automation infrastructure | RevOps |
| Today | AI wired into calls, CRM, ads and revenue | Operational AI |
Before "platform" was a default business model, we built one: a multi-tenant system for publishing mobile experiences at scale rather than building each one from scratch.
mobiManage was Bluefrog's own mobile platform and SaaS company. The engineering thesis was simple and, at the time, contrarian: mobile delivery was not a design project per client, it was an infrastructure problem. Build the rendering, content model, device handling and publishing pipeline once; let thousands of organizations configure it.
It powered mobile sites for tourism and convention & visitors bureaus, real estate — including Lennar's mobile launch in 2009 — restaurants and universities. The Journal Record named mobiManage Innovator of the Year in 2009, and Bluefrog's founder was appointed to the dotMobi Advisory Group, the industry body organized around the mobile web at the time.
The reason it belongs on this page is not nostalgia. It is the direct architectural ancestor of the Bluefrog Intelligence Platform: build the hard, shared machinery once, make it configurable, then extend it per company. If the platform solves 80% of the problem, we customize the remaining 20%. If the technology doesn't exist, we build it.
Archived deployment screenshots from the mobile platform era.
Bluefrog makes AI useful by integrating it with the way your business actually works — your software, your calls, your customers, your marketing and your revenue.
Technology development since 1997 · AI integration platforms since 2001
A real conversation with the people who build the technology — no obligation, no pressure.