Great teams have critical thinking and can explain cause and effect of their efforts

THIS PAGE IS OUTDATED

Marketing team - WE DON'T HAVE MARKETING TEAM AT THE MOMENT

• responsible for customer acquisition, which means attracting new users to use and pay for our product.
  • increasing new demand measured by net new revenue brought in each month
• Marketing is also responsible for customer communications. This means engaging with our users on a continuous basis.
• responsible for design and brand

Marketing team success

• Success can be measured by the actual new revenue earned, which should exceed our projected new revenues. When this happens, it indicates that the team's efforts are paying off, and they are bringing in significant growth.

  • It is not realistic to audit every user action down to the cause and effect of a click or view or engagement since a lot happens offline or is hidden behind privacy measures.

  While it may be challenging to track every user action, a successful campaign or activity that increases new revenues is a strong indicator of a successful strategy.

Developer Relations team - We don't have DEVREL TEAM AT THE MOMENT

DevRel team is newest team and information about this team can change. This info represent current initiatives.

DevRel team responsibilities

• creating and maintaining learning resources for people new to Codemagic
• advocating for Codemagic in developer communities

Developer Relations team success

• DevRel team is successful when people use learning resources we create and we see how it improves our monthly active users.
• DevRel team is successful when people recommend or show interest in codemagic because of developer relations engineers.

Product team

Product team responsibilities

• Product + dev team responsibility is maintaining and shipping product roadmap
• Maintain gross margin as agreed with CEO

Product team success

• New HA/week goes up (new product market fits)
• New features are being adopted by users
• Product uptime is good and we meet our SLAs with Enterprise customers

Open Source Engineering

Open Source engineering team responsibilities

• Work with Google to improve open source tools
• Maintain good relationships with Google

Open Source Engineering team success

• Show initiative in finding new ways to contribute and get more responsibility from Google team on existing projects and new projects
• Public praise from Google's side

Customer Engineering

Customer engineering team responsibilities

• Be responsible for helping customers who are interested to use our product
• Help users who are struggling to use our product
• Collaborate with product team to find ways to improve our product
• Improve and maintain our documentation to support self-serve product pillar

Customer engineering team is successful when

• New high-value customers per month metric is growing
• Users are able to self-service themselves without asking support for help