From startup to Fortune 100 — this is a sampling of what we've built.

Moen partnered with us to tech-enable its plumbing fixtures and build a modern smart water platform. We architected the entire Smart Water Cloud on AWS using serverless technology, supporting faucets, showers, and whole-house smart valves, plus the native iOS and Android apps that control them. The platform gives homeowners real-time visibility into water usage and remote control over every connected fixture from a single app, and the work went on to earn a CES Best of Show award — recognition for one of the most ambitious connected-plumbing ecosystems built to date.

For Honeywell, we build the Li-ion Tamer — an early-warning gas detection system that identifies lithium-ion battery failures before thermal runaway occurs. As lithium-ion batteries have become standard in everything from consumer electronics to grid-scale energy storage, this kind of early-warning capability has become critical safety infrastructure, giving facility operators the minutes of advance notice needed to evacuate or intervene before a battery fire can spread.

The first commercial release of Energizer's mobile app for Bluetooth-enabled lights, built end to end including BLE firmware and over-the-air update support. We handled the full stack — from the embedded BLE firmware running on the light fixtures themselves to the consumer-facing app used to pair, schedule, and control them — plus the OTA update pipeline that let Energizer patch and improve firmware on devices already in customers' homes.

We helped build TrainTime, the trip-planning and ticketing app for commuters, and MyMTA, which plans routes across Manhattan by bus, subway, and train — plus supported MTA's large-scale Salesforce implementation for customer relationship management. Both apps serve one of the largest and busiest transit systems in the country, where reliability isn't optional — commuters depend on accurate, real-time trip data every day. Our Salesforce work gave MTA's customer service teams a unified system for managing rider inquiries at that same scale.

The Gatorade Sports Science Institute, Gatorade's scientific arm focused on athlete nutrition research, needed iPad applications for athlete analysis studies that met strict research guidelines. We built the iPad solutions plus the cloud backend supporting complex admin functions. The apps had to capture consistent, research-grade data from athletes in the field, then sync it back to a cloud backend where GSSI's scientists could manage studies, review results, and administer access across research teams.

Movable was producing its 3rd-generation activity tracker with integrated Bluetooth LE. We built native iOS and Android apps and integrated the devices via a custom Bluetooth protocol syncing to their cloud backend. We built the custom Bluetooth LE sync protocol from the ground up to reliably move activity data off the wearable and into the cloud, alongside the native apps athletes used to view their progress — foundational work that carried through as the product line was later acquired.

MetLife Legal Plans needed a best-in-class service solution for a large, complex call center. We architected Service Cloud with the Service Cloud Console UI, MuleSoft API connections, custom objects, round-robin case assignment, and advanced geolocation functionality. The Console UI gave agents a single, unified screen instead of juggling multiple tools mid-call, while the round-robin routing and geolocation logic made sure cases landed with the right specialist automatically — cutting down on manual triage in a call center handling a high volume of legal service requests.

Managing explosive growth, Tiger Pistol needed one integrated system instead of disjointed tools. We implemented Sales Cloud, Service Cloud, and Marketing Cloud together, built custom advanced case routing and a bespoke time-tracking solution, then stayed on as their ongoing fractional Salesforce admin. Bringing all three clouds onto one connected platform meant sales, support, and marketing teams were finally working from the same data instead of three separate silos — and staying on as their fractional admin meant the system kept evolving alongside the business instead of going stale after launch.

We built a cross-platform application used internally with Hilton's franchise partners, integrating with and extending an existing Salesforce.com solution to provide two-way interaction with their customized CRM. Franchise partners needed a way to interact directly with Hilton's CRM data rather than working through headquarters for every update, so the two-way sync we built let information flow both directions — keeping franchise-level data and corporate records in step with each other.

We built iPad applications for Spectrum's sales teams, leveraging custom Salesforce.com implementations with integrated native apps to automate and optimize the sales process. Sales reps in the field needed the same account and product data available in the office, so the iPad apps tied directly into the underlying Salesforce implementation — replacing manual, paper-driven steps with a workflow that kept every rep working from current information.

Ford needed personalized site experiences and a unified content platform. Our team helped implement Adobe Target and Analytics for A/B and multivariate testing, plus a highly clustered AEM infrastructure with Akamai CDN — contributing to Ford's ranking among the top ten automotive sites for performance. The clustered AEM setup had to serve personalized content at automotive-industry scale without sacrificing load times, and the Adobe Target testing infrastructure gave Ford's marketing team a continuous way to measure what actually improved engagement.

GM was converting its websites to a global AEM platform with full authoring capabilities, mobile-first and consistent across every screen size. Our team contributed to the shared component library and supported the multi-tenant, multi-lingual architecture as it rolled out from North America globally. Rolling out to dozens of markets and languages meant the same component library had to hold up everywhere without fragmenting into one-off regional builds — consistency in that shared library was the difference between a scalable rollout and a maintenance headache.