Fractional CTO and fractional technical leadership
BlueMind's CEO lacked the technical visibility to understand why the offshore team kept missing deadlines, and hiring a full time CTO was not something the budget could support yet. Ollon stepped into that role on a fractional basis, meeting directly with the CEO on decisions like whether to keep MariaDB or move to MySQL, and translating the offshore team's technical status into terms the CEO could act on. That direct line gave the CEO a way to assess progress and make calls about the platform's direction without carrying a full time executive salary. BlueMind kept its offshore cost structure while finally getting the technical oversight it had been missing.
Team mentoring and coaching
BlueMind's offshore team needed more context on how individual tickets connected to the bigger picture, and deadlines slipped as a result even though effort was never the issue. Ollon ran a standing cycle of code reviews and design reviews on every pull request, walking through specific bugs, like a failed database migration, directly with the developer who wrote it instead of simply fixing it and moving on. Over time, the same categories of mistakes stopped recurring in review, a sign the coaching was landing and not just patching each issue as it came up. That shift let the offshore team take on more of the platform's development with less oversight needed.
Team augmentation and staff scaling
BlueMind needed different amounts and kinds of technical support at different points over more than two years, from heavy infrastructure work early on to lighter, leadership only oversight later as the platform stabilized. Ollon adjusted its own team size and mix to match, moving from a larger group covering DevOps, backend, and QA support down to a lean pairing of a project manager and technical lead once the platform reached a steady state, while also sitting in on interviews for BlueMind's own offshore hires to review resumes and help assess candidates before they joined the team. That flexibility let BlueMind pay for the capacity it actually needed at each stage instead of a fixed team sized for its busiest month.
Fractional DevOps support
Separate staging and production environments for BlueMind's USA and Canada applications meant a failed database migration could slip into a deployed build undetected. Ollon rebuilt the CI/CD pipeline to spin up a test database during every build and fail it outright if a migration broke, extended the Terraform infrastructure to manage environment variables and secrets consistently across both country deployments, and added structured logging to logz.io along with a Slack channel that surfaced application errors as they happened. That infrastructure work gave BlueMind deployments it could trust would either succeed cleanly or fail loudly before reaching customers.
Code review and design review
Architecture decisions and day to day code changes at BlueMind both needed a second set of eyes before they shipped, but a schema change carried more risk than a routine bug fix and needed different handling. Ollon split the review process in two, folding routine code review into the normal pull request cycle while holding separate sessions for decisions that touched more than one part of the system. That separation meant a small fix did not wait behind the scrutiny a bigger change required, while wider impact decisions still got dedicated time and the right people involved. The result was a codebase where problems surfaced during review, without every small change slowing to the pace of the big ones.
Security and compliance consulting
Security groups, S3 buckets, and databases in BlueMind's AWS environment had grown without much attention to how they were actually locked down, a gap that mattered more once the platform needed to meet insurance industry standards. Ollon audited the existing security group rules and rebuilt the relevant Terraform infrastructure to tighten access to S3 and RDS, then ran dedicated security reviews to work through the tickets that came out of that process. That hardening work gave BlueMind an AWS environment built to hold up under the scrutiny its insurance broker customers required. It also gave the CEO something concrete to point to when customers asked how their data was protected.
Agile / Scrum / Kanban
A predictable rhythm of planning and check ins was missing for BlueMind's offshore team, part of what had stalled the MVP before Ollon got involved. Ollon established daily standups and regular scrum sessions with the offshore team, running sprint planning and backlog review as a consistent cadence, not something that only happened once a deadline was already at risk. That structure gave the CEO visibility into what the team was working on day to day, not just when something went wrong. The missed deadline pattern that had defined the project before became the exception instead of the norm.
Technical architecture
Duplicate migrations and an unclear database structure had piled up by the time Ollon evaluated whether BlueMind should stay on MariaDB or move to MySQL for better long term support. Ollon audited every existing migration, merged the duplicates into a single clean set, and reorganized them into separate folders for the USA and Canada applications plus a shared folder for what both used. That cleanup also supported a new base infrastructure letting the USA application share the same database and network as Canada instead of duplicating both from scratch. The result was a data layer that could support two country deployments without maintaining two separate sets of migrations and infrastructure code.
Chargebee
Subscription billing for BlueMind ran through Chargebee, and keeping that integration working across the USA and Canada environments meant keeping a growing set of API keys and configuration values in sync in AWS. Ollon added and maintained the environment variables Chargebee needed in each staging and production environment, then debugged integration issues directly when billing behavior did not match what the platform expected. That work kept subscription billing running reliably as BlueMind's infrastructure and customer base grew. It also meant billing problems got caught and fixed before they affected a customer's account.
