Writing About ScaleMath

A Quick Primer on ScaleMath

In short: We operate & advise industry-leading software companies.

What this means in most cases: ScaleMath runs growth for your favorite companies.

In some cases: We operate companies we own (partially or entirely).

Learn more about the ScaleMath Mission & Vision in our employee handbook here.

Brand Name 

The brand name is ScaleMath, always written with a capital S and capital M.

Unless referring to the domain name, in which case all lowercase should be shown as:

https://scalemath.com

Not any of the following: 

  • www.scalemath.com
  • http://scalemath.com
  • http://www.scalemath.com
  • https://www.scalemath.com

scalemath.com (this is accepted if a particularly short or minimal graphic is required where the space doesn’t allow for the fully qualified URL to be included) 

A Breakdown of ScaleMath’s Business Model

We operate two core models:

  1. We partner 1:1 with companies on our advisory & services side.
  2. We operate software companies entirely.

The companies we are best suited to serve are software companies (primarily B2B) that are approaching or beyond 500k in ARR (annual recurring revenue).

Language and Spelling

All spelling and grammar in messaging should be according to US English.

Voice

When writing for ScaleMath and references to the ‘author’ should be written in the first personal plural – ‘we’, ‘us’, ‘our’.

All references to the reader should be written in the effective first person singular – ‘you’, ‘your’. Unless referring to a specific example that includes someone of either male or female gender (in which case respective pronouns may be used), the general neutral they should be used. This is completely irrespective of anyone’s beliefs on this matter. It is good practice to do so, and this has been the case long before 2020 🙂 – it never made sense for UI copy to include tooltips that state “he” as users were always capable of being male or female. 

We much prefer informal language and paragraphs that aren’t longer than 3-4 lines (as a general rule, not a requirement). Essentially, write how you talk and cut through the bullshit. 

“it’s” preferred over “it is”. 

Blog Post Conclusions

The heading for the conclusion/summary section should follow this general format: 

  • Summary –  Should You Use FTP or SFTP?
  • After Action Report — Install WordPress Locally To Simplify Your Development Workflow
  • After Action Report – Getting Started with GitHub
  • Conclusion – Use Cloudflare Firewall Rules To Your Advantage

After which, depending on the article, we will write a summary – including asking a question, inviting them to connect with us on social, including a call-to-action (CTA), directing readers to other relevant resources (of our own or from others). This will vary from post to post. At the very end, we always invite readers to join the conversation, example: 

Let us know & join the conversation by Tweeting at us! How do you currently handle scope creep with your clients? 💬

Updated on February 15, 2024

Related Articles