Skip to content
24Squad

Methodology

Methodology

Published 2026-07-14Reviewed 2026-07-19Reviewed quarterly

Reviewed by Renish Mithani — Founder & CEO, on 2026-07-19.


Overview

This page documents how we choose what to write, how we source statistics, how we evaluate and rank partners and recommendations, and how we decide which 24Squad ventures to write about. We publish this methodology so readers can judge our work on its merits — and so we can be held to it.

Topic selection

We cover four areas of the Indian startup ecosystem:

  1. Founders — first-person playbooks on building, fundraising, and operating in India, written by named 24Squad founders.
  2. Financing — Indian venture capital, debt funding, and government-funding programs (Startup India, MSME, CGTMSE).
  3. Regulatory landscape — GST, income tax, Companies Act, Shops and Establishments Act, and other compliance regimes relevant to Indian SMBs.
  4. Group-specific research — operating knowledge from the 24Squad ventures (FinTax24, 24Square, WebGrow24, WebHost24, Rozgar24) that is useful to founders and operators outside the group.

We do not cover: stock recommendations, crypto token analysis, consumer-product reviews, or any topic where we cannot bring demonstrable operating experience.

Statistics

  • We prefer Indian-government and Indian primary sources (CBIC, RBI, DPIIT, MCA, GSTN).
  • We cross-reference every statistic against at least one independent secondary source before publication.
  • We date-stamp every statistic with the publication or access date.
  • We do not cite statistics from SEO farms, listicles, or content syndicators without checking the underlying primary source.
  • Where a statistic is contested or has been revised, we link to both the original and the revision.

Recommendations

When we recommend a service, tool, or partner, we:

  1. State the reason for the recommendation in the first sentence of the relevant paragraph. No bury-the-lede.
  2. Disclose any commercial relationship in the same paragraph. We never recommend a service we have a paid relationship with without disclosing the relationship.
  3. Explain how the recommendation was evaluated. The evaluation criteria are reproducible: we publish the rubric where applicable.
  4. Date-stamp every recommendation. Recommendations can go stale; an undated recommendation is a red flag.

Partner evaluation rubric

24Squad ventures work with service partners (lawyers, accountants, designers, agencies). When we publish a case study that names a partner, the partner must meet the following criteria:

  • The partner has a registered business entity in India (GSTIN or LLPIN).
  • The partner has a verifiable track record of at least 12 months in the named service.
  • The partner has at least three named reference customers we have contacted.
  • The partner carries professional indemnity insurance where the service exposes us to material risk.
  • The partner has signed our standard data-handling agreement.

Partners who fail any of these criteria are not named in published case studies even if we used them.

How we evaluate 24Squad ventures

When we write about a 24Squad venture, the post covers:

  • The venture’s founding date, registered entity, and HQ address.
  • A named founder with a profile page on the site.
  • The venture’s three core metrics (revenue, customers, retention) as of the post’s publish date, or an explicit “metrics are not disclosed” note with the reason.
  • A “What we got wrong” section if the venture has had a public failure mode (rejected feature, customer churn event, regulatory issue) that the post would otherwise gloss over.

Updates and re-reviews

This methodology page is reviewed quarterly. The reviewer’s name and review date are recorded in the frontmatter and emitted in the reviewedBy JSON-LD field. Substantive changes are logged in the CHANGELOG.

This page was reviewed by Renish Mithani on 19 July 2026.

Let's build

Want to know more about 24Squad?

We answer general inquiries within 2 business days. For venture-specific needs, use the contact details on the relevant page.