Superkind for software companies

In a software company tickets pile up, release notes need writing, customers need informing about updates and documentation needs to stay current. You hand this work to Superkinds. You describe it once in Slack, Teams or by email, they do it in your tools, and nothing goes out before you approve it.

Superkind Team

Every example is set at Schneider GmbH, a made-up company

Meet the software company Superkinds

Four Superkinds, each with one clear job. They all share the same company knowledge, so the Customer Notifier knows the release details from the Release Planner

One release, from planning to customer notification

How a product update at Schneider GmbH Software runs through the four Superkinds

YouSlack

@Superkind Version 4.2 goes live next week. New filter feature and three bug fixes. Handle everything except the development.

  1. Ticket Collector

    collects completed tickets and writes the release notes

    Release notes v4.2
  2. Release Planner

    plans the schedule and checks the checklist

    Release plan With your approval
  3. Customer Notifier

    notifies customers about the update

    Customer message With your approval
  4. Docs Updater

    updates the documentation and the help center

    Docs updated
Result

The release is out, customers are informed, docs are current.

JiraSlackGoogle Docs

Ticket Collector: knows what is in the release

Reads completed tickets from Jira, sorts them by features and fixes and writes the release notes in Google Docs

product
You9:00

@Superkind What is in v4.2?

Ticket CollectorSuperkind9:02

One feature and three bug fixes. Draft release notes ready:

  • New filter feature Feature
  • Export bug fixed Bug fix
  • Dashboard load time Bug fix

Set up in three steps

  1. Write in Slack: "@Superkind, I need a Ticket Collector. Collect completed tickets before every release and write the release notes."

  2. Connect Jira and Google Docs. Superkind reads the tickets and writes the notes into the template.

  3. Say when it runs: "Three days before every release." Superkind saves it as a routine.

JiraGoogle CalendarAsana

Release Planner: keeps the schedule on track

Creates the release schedule, assigns tasks to the team and checks the day before go-live that everything is done

Product
You10:00

@Superkind How is the release plan for v4.2?

Release PlannerSuperkind10:02

Plan is set. Two tasks still open:

  • Staging test open, assigned to Mia Waiting for you
  • Check migration script open, assigned to you Waiting for you
  • Release notes done Done

Set up in three steps

  1. Write in Teams: "@Superkind, I need a Release Planner. Create the schedule and check the checklist before every release."

  2. Connect Jira, Google Calendar and Asana. Superkind sees tickets, dates and tasks.

  3. Confirm the rule: the release plan waits for your approval before it goes to the team.

HubSpotMailchimpOutlook

Customer Notifier: gets the update to the customer

Takes the release notes, writes the customer message and sends it via Mailchimp to all active customers

product
You14:00

@Superkind Write the customer message for v4.2.

Customer NotifierSuperkind14:03

Message is ready. Goes to 340 active customers. Shall I send it?

Update v4.2340 recipients · 1 feature, 3 fixes

Set up in three steps

  1. Write in Slack: "@Superkind, I need a Customer Notifier. Write the customer message after every release."

  2. Connect HubSpot and Mailchimp. Superkind knows which customers are active and uses the email template.

  3. Set the rule: "No customer message goes out without my approval."

Google DocsFreshdeskSharePoint

Docs Updater: keeps the docs up to date

Takes the release notes and updates the affected pages in Google Docs and the help articles in Freshdesk

Product
You15:00

@Superkind Update the docs for v4.2.

Docs UpdaterSuperkind15:04

Three pages updated, one new help article created:

  • Filter page new feature documented Done
  • Export page bug fix note added Done
  • Help: "How do I filter?" newly created Waiting for you

Set up in three steps

  1. Write in Teams: "@Superkind, I need a Docs Updater. Update the documentation after every release."

  2. Connect Google Docs and Freshdesk. Superkind knows which pages are affected.

  3. Say when it runs: "On release day." Superkind saves it as a routine.

Frequently asked questions

Can Superkind write code or fix bugs?

No. Superkind handles the work around development: release notes, schedules, customer messages and documentation. Development stays with your team.

Which tools do I need?

The ones you already have. Superkind has 1,700+ integrations, including Jira, HubSpot, Mailchimp, Freshdesk and Google Docs. Nobody has to learn a new tool.

Do the Superkinds know about each other?

Yes. What one Superkind learns goes into your company knowledge. So the Customer Notifier knows the release details from the Ticket Collector.

What does it cost?

You can try Superkind for free, with up to 150 hours of work and no credit card. Business starts at €50 a month for unlimited users. €1 gets about one hour of work done. Every plan is on the pricing page.

Is my data safe?

Superkind keeps storage and AI models in the EU, is GDPR compliant and aligned with the EU AI Act. No model is trained on your data.

More use cases

The other departments and their Superkinds

Ready for your first AI employee?

Try Superkind