Blocks

Name: Blocks
Brand: Blocks

AI Native

Blocks is a cloud cost optimization service that reduces AWS spend by combining an aggregated group-buying model to negotiate volume discounts with an automation engine that identifies waste and can execute optimizations under configurable guardrails.

Est 2025|Valuation $34.6M|Raised $5.8M

Website|FTEs 20

MarketsCloud Management & FinOps Cloud Cost Management

Published Sep 30, 2026

01Common complaints

- When first-class multi-cloud optimization (AWS + Azure + GCP) is a primary requirement - Alternatives such as Apptio Cloudability, Vantage, or CloudZero may better meet that need. - When detailed unit-economics / cost-per-customer / per-feature allocation is the primary requirement - CloudZero and some enterprise FinOps platforms are typically stronger in detailed allocation and business mapping. - When the organization cannot or will not transfer AWS billing to a reseller - The group-buying/reseller mechanism may be impractical without billing transfer. - When vendor onboarding requires published SOC 2 / ISO 27001 documentation - Public pages reviewed did not include those certifications; absence may delay or prevent procurement approval. - When the environment is already heavily optimized with a mature FinOps program and commitment strategies - Incremental savings opportunity may be limited, reducing the attractiveness of a success-fee model. - Publicly observable limitations - Limited independent public review content for Blocks makes third-party validation difficult. - Security and compliance posture is not clearly documented via public certifications in the accessible sources. - The group-buying discount is contractually described as variable and influenced by external program terms and the composition of aggregated usage. - Roadmap disclosures - No public roadmap with dated commitments was found in accessible sources.

Reasons some customers might leave for competitors (plausible churn reasons)

Requirement for first‑class multi‑cloud optimization (AWS + Azure + GCP) that Blocks does not clearly advertise.
Need for deep unit‑economics and allocation analytics rather than primarily discounting and tactical waste cleanup.
Preference for self‑serve tooling with full transparency and control over changes.
Procurement or security requirements that demand mature, publicly documented security certifications and controls.

02Why they buy

- Vendor-stated differentiators (reported without endorsement) - The vendor presents a guaranteed 20% savings target on AWS through a combination of negotiated discounts and optimization actions. - The vendor states it aggregates spend across multiple customers to negotiate volume discounts. - The vendor offers an automation component that identifies waste and can execute optimizations under configurable guardrails. - Critical validation notes - These claims were not corroborated by audited methodologies, published customer case studies with independent validation, or independent benchmarks in the accessible sources. - Buyers should request: - Written guarantee terms and any exclusions - A clear definition of what constitutes "optimizable spend" and exclusions (e.g., marketplace, support fees, taxes) - Documentation and evidence of realized savings calculations and governance over when an action is considered completed - Areas where competitors have clear advantages - Competitors may provide broader multi-cloud coverage, deeper allocation and unit-economics tooling, and more mature security documentation.

03Field reports

Overall availability of independent reviews

Blocks (official product site) has limited presence on mainstream B2B review platforms under that exact product name/domain in accessible search results.
A procurement risk for buyers is that public independent reviews and third‑party validation are limited; purchase evaluations may rely on vendor claims and private reference calls.

Direct quotes (balanced) from accessible sources

Limited verifiable Blocks‑specific end‑user quotes were found on major review platforms during this research.
To provide context, the report references broader market sentiment about cloud cost optimization tools, which reflects common buyer concerns even if not Blocks‑specific.

Representative community criticisms of cloud cost tools (context for Blocks)

Example critiques identified in cloud and startup forums include:
- Some practitioners describe many cloud cost optimizers as dashboards that surface data without sufficiently supporting remediation.
- Skepticism about the proliferation of cost tools and the value delivered beyond increased visibility.

Reasons customers might choose Blocks (inferred from positioning)

Preference for a rate‑optimization approach that focuses on volume discounts via aggregated buying power.
Desire to avoid fixed subscription fees when ROI is uncertain; success‑fee alignment can be attractive for that buyer profile.
Limited internal DevOps/FinOps capacity and an interest in automated recommendations with configurable guardrails.

Vendor-published examples (not independently verified)

The product marketing site provides illustrative examples such as deleting an idle NAT Gateway and recommending Terraform fixes for security exposures.
These examples are illustrative; they do not disclose baseline environment details, methodology, or audited long-term realization of savings.

Independent case studies

No independently validated Blocks customer case studies with named customers and externally verifiable metrics were found in accessible sources.

04Best fit

Ideal Customer Profile

- Company sizes (practical ranges) - Likely best fit: - Small to mid-sized organizations - AWS spend at a level where a meaningful percentage reduction is materially significant — organizations with moderately high monthly cloud spend, though the break-even point will vary - Industries/verticals - SaaS, internet businesses, developer-first products, and companies that are AWS-native with rapidly changing infrastructure. - Roles and personas - Economic buyers: VP Engineering, CTO, Head of Infrastructure/Platform, and in some cases CFO/Finance Ops. - Daily users: DevOps/SRE, platform engineering, FinOps practitioners. - Pain points - Rapid cloud spend growth, limited internal expertise on commitment optimization, and operational complexity that prevents teams from keeping costs controlled. - Qualification criteria (good fit) - AWS-centric workloads - Willingness to consider a billing transfer/reseller arrangement - Appetite for automated recommendations and configurable guardrails - Deal disqualifiers (poor fit) - Requirement for first-class multi-cloud optimization - Procurement/security policies that require publicly documented compliance certifications - Organizations unwilling to change billing relationships

05The pitch

What the product does (core value proposition in objective terms)

- Blocks describes a service aimed at reducing AWS costs using two primary mechanisms: - A group-buying / aggregated spend model intended to obtain volume discounts on AWS pricing. - An automation component (marketed as "Major Tom") that identifies waste, surfaces recommendations, and can optionally execute optimization actions under configurable guardrails. - The marketing site presents a vendor-stated cost savings guarantee (a specific percentage is claimed) and asserts that onboarding can be completed quickly via read-only access to AWS cost & usage data followed by an optional billing transfer to the vendor.

Target market and market positioning

Blocks targets growth-stage companies and positions itself as a membership-based community where aggregated customer spend is used to negotiate volume discounts. This positioning implies a bias toward:
- Startups and scaleups with meaningful AWS spend
- Organizations that prefer a low-touch discounting approach combined with automated waste remediation rather than building a full internal FinOps function

Get a comprehensive analysis of Blocks including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →