Client background
UnlikelyPlaces is a Portland, Oregon-based digital consulting practice led by CEO Jay M., specialising in digital product development and brand marketing for Fortune 500 and Fortune 100 companies in the mobile and sports sectors. As a consulting practice, UnlikelyPlaces creates and manages complex digital product builds for enterprise clients, operating at the intersection of strategy, design, and engineering.
The engagement with Squash Apps began when UnlikelyPlaces needed a development partner for one of their most ambitious projects: the engineering of an MVP for a sports philanthropy platform. The platform was designed to bring a novel sports philanthropy business model to market — a platform that would connect the commercial power of professional sports brands with charitable causes in a way that created genuine fan engagement rather than the passive donation model that characterises most sports charity work.
The scope was genuinely enterprise-grade: a web application, a mobile application, and robust backend mechanics capable of handling the transaction volumes and real-time engagement features that live sports events generate. The engineering challenge was matched by the commercial stakes: this was a platform intended for Fortune 100 partner deployment, where reliability, scale, and the quality of the user experience were non-negotiable.
The challenge
Jay M.'s challenge was finding a development partner who could operate at the standard required by Fortune 500 enterprise clients. The sports philanthropy platform had to meet a quality bar that most offshore vendors cannot reliably achieve: complex backend mechanics, real-time features, mobile and web parity, and the kind of code quality that would hold up to technical review by the enterprise clients' own engineering teams.
Previous experiences with offshore development vendors had taught UnlikelyPlaces what to look for and what to avoid. The common failure modes — strong sales presentation but weak technical execution, good performance on simple tasks but breakdown on architectural complexity, and cultural misalignment that made communication difficult under pressure — were patterns Jay had seen before and was determined to avoid. The partner he needed had to be technically excellent, communicative in a way that bridged cultural distance, and capable of the long-term relationship that a $600k+ multi-year engagement requires.
The technical scope itself was demanding. The backend mechanics needed to support real-time charitable contribution tracking during live sports events — a use case with sharp traffic spikes and consistency requirements (every user's contribution needs to be accurately recorded, and the real-time totals displayed to fans need to be trustworthy). The mobile application needed to deliver a sports fan experience with the performance and quality standards that users accustomed to the best sports apps in the market would expect. The web application needed to be equally polished for enterprise partner users.
The 18-month deployment timeline was a hard constraint: the platform needed to be in beta by a specific date that was tied to a major sports season.
How we engaged
Squash Apps was introduced to UnlikelyPlaces through a former business partner. The selection process was thorough: Jay M. and his team vetted several engineering firms, had multiple meetings with each, and specifically used test projects to evaluate technical capability before committing. Squash Apps outperformed the alternatives on the test project, and the relationship that would grow to over $600,000 in engagement value began.
The team composition varied by sprint phase, typically ranging from 6 to 14 people: backend engineers, frontend engineers, mobile engineers, QA specialists, a system architect, and project managers. Srijith was involved throughout — not in a nominal "executive sponsor" capacity, but as an active participant in architecture decisions, sprint reviews, and the ongoing dialogue about technical trade-offs that defines the working relationship on a complex engagement.
Jay M.'s description of what differentiated the engagement is worth quoting in full: "Squash Apps is far superior to other offshore firms we've experienced in terms of quality and timelines. They've proven their skills and capabilities over and over again." This wasn't a one-sprint assessment — it was built over multiple years of consistent performance through genuinely complex engineering challenges.
Communication quality was a specific standout: "Communication has been great, and there's no language disconnect because they have a solid grasp of the English language." On an engagement working with Fortune 100 enterprise client requirements, where imprecision in communication can generate expensive rework, the quality of written and spoken communication is not a minor consideration.
What we built
The MVP platform comprised three interconnected products. The web application served enterprise partner users — sports organisations, brand sponsors, and charitable partners — with tools for configuring philanthropy campaigns, setting contribution matching rules, tracking real-time campaign performance during live events, and accessing post-event reports. The interface was designed to meet the professional standards expected by Fortune 500 marketing and sponsorship teams.
The mobile application delivered the fan-facing experience: real-time charity contribution tracking during live games, leaderboard displays showing cumulative contributions from different fan communities, social sharing mechanics for contribution milestones, and notifications tied to game events (goals, touchdowns, key plays) that triggered contribution matching opportunities. The real-time requirements were demanding: fan-facing totals needed to update within seconds of a contribution being recorded, and the experience needed to be reliable during the peak load moments that coincide with the most exciting moments of a live game.
The backend mechanics — the term Jay M. used to describe the platform's core infrastructure — handled the transaction processing, matching rules engine, real-time aggregation, and integration with the charitable disbursement systems that would ultimately route contributions to partner charities. This backend was designed and built with the scalability requirements of a major sports event in mind: the load profile during a game day is dramatically different from a quiet Tuesday, and the system needed to handle the peaks without degradation.
The system architecture work — led by the Squash Apps architect in collaboration with the UnlikelyPlaces technical leadership — established the foundational patterns for how the entire platform would be built, deployed, and scaled. These architectural decisions made in the MVP phase would prove to be sound as the platform grew through subsequent phases.
Technical approach
The platform was built on a React/Node.js stack, with React Native for mobile and a distributed backend architecture on AWS designed for the event-driven, high-peak traffic pattern of live sports.
The real-time contribution aggregation used an event sourcing architecture: every contribution was recorded as an immutable event, and the real-time totals displayed to fans were computed from the event stream rather than from a mutable counter. This approach eliminated the concurrency issues that would arise from multiple users simultaneously incrementing a shared counter, and provided a complete audit trail of every contribution that was essential for charitable compliance reporting.
The matching rules engine was implemented as a configurable rule evaluation system: sponsors could define complex matching conditions (e.g., "match all contributions during the second half, up to $X total, with a 2x multiplier for contributions from fans in the home city"). Rules were evaluated asynchronously to avoid adding latency to the contribution recording path.
AWS infrastructure used auto-scaling ECS Fargate tasks for the application tier, ElastiCache for the real-time aggregation layer, and Aurora PostgreSQL for the core data store. Scaling policies were designed around the event traffic pattern rather than CPU or memory thresholds, using game schedule data to pre-scale ahead of known high-traffic windows.
Results
The platform was delivered on the 18-month timeline, with the beta milestone met as planned. Jay M.'s assessment: "Squash Apps has exceeded our expectations, working long hours, producing more than is asked of them, and working much faster than is standard in the industry." Specifically on timeline performance: "They have finished ahead of schedule every time."
The engagement has continued well beyond the initial MVP scope, growing to over $600,000 in cumulative value across multiple phases of product development. The consistent performance over multiple years — on an engagement with genuine enterprise-grade requirements — is the clearest possible evidence of the quality of the partnership.
The platform's technical architecture has scaled alongside the commercial growth: the event sourcing approach for contribution recording, the pre-scaling infrastructure policies tied to game schedules, and the configurable matching rules engine have all proven to be sound investments that enabled feature additions without architectural rework. Building for scale from the start, rather than retrofitting it later, was one of the most consequential technical decisions of the engagement.
Jay's advice to potential customers captures the dynamic that made the engagement work: "Give them a test project to see how you work together. They can compete with big companies but are agile and entrepreneurial in their client interactions." For digital agencies, consulting firms, and product studios handling enterprise clients who need a dependable offshore engineering team capable of working to Fortune 500 standards, the UnlikelyPlaces engagement is the reference case.