Flexible software cost capitalization reporting

You can get started with Swarmia by scheduling a meeting with one of our product experts. They’re happy to give you a tour of the product, answer any questions you may have, and work with your team to tailor a trial/POC plan for your organization.

If you’re interested in using Swarmia for software capitalization reporting, contact your account manager or email us at hello@swarmia.com.

In practice, the process looks like this:

• You’ll configure your investment categories in Swarmia to capture capitalizable work. If you need a hand in setting up investment categories, your customer success manager would be happy to help — at no extra cost. We’ll also review your team roster and capitalizable investment categories.
• You’ll inform your customer success manager of your specific requirements for the report, including its cadence and scope.
• You’ll receive the report at a regular cadence. You’ll be able to adjust the report to include exact salary data from your HR system, and to manage exceptions on a per developer or project basis.

Swarmia models developer effort on a monthly basis from activity such as issue completions, pull request merges, reviews, and commits. In other words, we combine each engineers’ code contributions from GitHub with their issue tracker activity from Jira or Linear. By automatically attributing individual work items to their highest known parent issue, Swarmia provides you with reliable and transparent data.

Instead of having to import data from your HR system directly into Swarmia, you can easily join salary or salary band data exports into the spreadsheet reports you’ll receive from us.

This way, you remain in full control over who gets access to the salary data.

Anyone in your organization with GitHub credentials can access Swarmia.

Finance and accounting teams as well as external auditors typically interact with Swarmia through the PDF and spreadsheet-based cost estimation and software capitalization reports.

Absolutely. Reach out to hello@swarmia.com or your account manager to get your copy.

We’re happy to share the report with anyone we have a legitimate business relationship with. If you’re a security team member looking for an answer to this question, please make sure that your point of contact for the Swarmia evaluation has talked to your account manager about it.

We’d be happy to complete a security questionnaire for any company considering one of our paid plans. Please reach out to your account manager or hello@swarmia.com to get started.

Swarmia supports Single Sign-On through GitHub.

Swarmia requires all users to log in to the product using their GitHub login. This allows us to avoid security hurdles with self-managed passwords and use an identity provider that your organization already trusts.

The typical Single Sign-On features work through the GitHub authentication:

• You’ll be able to get access to Swarmia when you have access to the relevant GitHub organization, so you don’t need to create Swarmia user accounts for each employee.
• When an account is disabled from your SSO provider, if you’ve configured it to be deleted from GitHub the change will also propagate to Swarmia automatically.

In our experience, this solution should pass a review from your internal security team. Feel free to reach out to your account manager if you have any concerns, as we also have plans to support SSO providers directly.