Our Approach

From white-boarding cutting edge architectures to providing long-term support, we've developed the processes and implemented the advanced solutions that will solve your business needs. We call this SweetOps and it's a comprehensive plan for how we approach every engagement with our clients. It's a form of DevOps that enables companies to collaborate on infrastructure across corporate boundaries by using a shared library of Open Source infrastructure code developed and maintained by Cloud Posse. It's a framework for creating and building consistent platforms to be shared across team environments. Everything we create is Open Source (APACHE2) and free to use—no strings attached.

Here’s a sneak peek at what that looks like.


We work closely with your CTO/VPE and engineering teams to architect solutions that will support your current needs and strategic initiatives. It’s our top priority to establish a strong rapport with your team by earning their respect. We promote efficient collaboration with as little management overhead as possible because we understand developers (we are developers). A strong emphasis is placed from the very beginning on cross-training engineers to hone their operational competency so that they have the necessary skills to triage critical problems, setup development sandboxes and even handle production environments.

Here’s how we go about it.

Small Teams

We believe that small cohesive teams stand the greatest chance of long-term success. This is because autonomous, self-organizing teams are able to avoid undue bureaucracy and micromanagement.

Direct Collaboration

No one understands your business better than you. Therefore we listen to your engineers and strive to understand your business requirements so that we can work together to solve your problems. Everyone on your team adds value to the project.

Flexible Process

Executing well is a skill. Working with good people and teams trumps any rigid process. The goal is always the same – to consistently deliver on time. One-size does not fit all, which is why our “Agile” ensures your needs are met providing the greatest likelihood of a successful outcome.

No Middlemen

We cut out the middlemen. By working with us, you always have a direct line of communication with anyone on our team via Slack, Email, and Jira. There's no complicated management structure or process involved with getting in touch with us or the help you need.

Our Posse + Your Team = Collaboration

Cloud Architect / Solutions Architect

Our Senior Cloud Architect leads the overall technical vision and implementation of the cloud architecture from beginning to end. They have vast cross-domain expertise and are capable of bridging the gap between business and technology. They are responsible for overseeing the project until completion and will participate in all calls and demos.

DevOps Engineer (1-2)

Our Senior DevOps engineers have vast experience working with a wide array of cloud-native technologies and are responsible for hands-on implementation, deployment and orchestration/automation of the infrastructure. They'll pair heavily with your team to get them up to speed on the complete technology stack.

Release Engineer

Our Release Engineers are responsible for designing the end to end CI/CD pipeline with Docker compositions for integration testing and continuous delivery pipelines. This includes designing piplines for “Preview Environments” spun up for every branch or PR, as well as the pipelines for staging and production environments.

Our Process

Research & Discovery

  • 01

    Work with you to perform a comprehensive Technical Audit to inventory the entire stack, covering all components and external systems or backing services in-scope for migration.

  • 02

    Conduct thorough Stakeholder interviews to learn what has worked well in the past and uncover the current pain-points, because no one understands your business better than you.

  • 03

    Identify and codify all Technical & Business Requirements, including the financial motivations, departmental budgets as well as technical motivations for the project so that we can achieve success.

  • 04

    Review existing design documentation and code repositories. Identify what is re-usable and what will need to be tweaked in order to be compatible with an elastic cloud environment.

Game Plan

  • 01

    We'll work with you to fast-track a comprehensive “Statement of Work” that will describe what we want to achieve and how we'll do it. We'll iterate on this using a shared Google Document until everyone is excited about the outcome.

  • 02

    Execute Master Services Agreement that describes the overall expectations of working with us; a Mutual NDA that describes how confidential material will be handled; then sign the Statement of Work to get started.

  • 03

    We'll establish the well-defined project plan in Jira with relevant timelines for when significant deliverables from the Statement of Work will be completed, as well as any major “Design Decisions” for your input.

  • 04

    We provide total transparency throughout the process. You'll have direct access to our Jira Cloud, up-to-date time reporting from Harvest, and see Pull Requests in your organization from Day One.

2-Week Sprints

  • 01

    Our “agile” development process is designed to help us better parallelize work to achieve aggressive timelines. You'll have access to Jira from day-one and follow along in our Slack channels.

  • 02

    Every week knock off significant deliverables (aka “Small Wins”) tied to the Statement of Work. We demonstrate continuous real-time progress in the form of git check-ins, Pull Requests, status updates, and documentation.

  • 03

    We hold regular weekly or bi-weekly calls via recorded Zoom sessions to review “Design Decisions”, give product demos, answer questions, and update the project's status so the organization can stay informed.

  • 04

    At any time, our priority is to unblock developers when issues come up. We see our role as enabling developers to do their jobs better, which is also why we place significant emphasis on documentation and collaboration.

“Go Live” Launch Preparations

  • 01

    Develop a comprehensive Go-live Plan. The checklist will address everything that needs to happen up to the point we flip the switch to make the system live. It will also include a rollback plan because we can never be 100% certain.

  • 02

    Verify all Monitoring & Alerting escalations are in place. Define responsibilities for the On-Call Engineer (OCE) and setup PagerDuty rotations. Establish processes for communicating outages and conducting postmortems of outages.

  • 03

    Conduct a final security audit to review security groups, access controls, and key rotation.

  • 04

    Support with VPC Peering to legacy environments and data migration to new environments.

Support &

  • 01

    We stay engaged for as long as it takes, as part of our continued investment in your company’s success. Your team can rest assured there’s an expert ready to assist them via Slack or Zoom. Need some help configuring a new service? No problem.

  • 02

    Life-cycle management is inevitable with any large scale infrastructure. This includes assisting with upgrades and addressing/patching bugs as they come up or suggesting improvements to your workflows as new technologies come along.

  • 03

    Perform periodic audits or reviews to ensure everything is working right. Ensure the cloud spend fits the budget. Produce cloud spend forecasts and implement cost controls.

  • 04

    Prepare any/all documentation that you request. Typical examples include diagrams of cloud architecture, including the various components, flow charts of network traffic and complex processes, and other visual aids.

Frequently Asked Questions