Talk about your next project
Red Hat case study

The lesson

Frame the case study around the human access problem first, then show the platform and products as the reason the operating change became possible.

The move

The story opens with the label “Success Story,” the headline “Banco da Amazônia S.A. brings financial services to remote populations with Red Hat,” and a blocked video module. An “Overview” explains BASA Digital and Banco da Amazônia S.A.’s role in the Amazon region, beside a profile card with “INDUSTRY,” “REGION,” “HEADQUARTERS,” and “SIZE.” The story then moves through “Challenge,” “Solution,” and “Business outcome,” using quotes from Roberto Schwartz and a product list headed “Software & Services used by Banco da Amazônia S.A.” The outcome section leads with the shift from processes that once took “6 months” to “24 hours,” then adds figures for contracted value, PRONAF contracts, signed contracts, rural credit, and award recognition.

Why it works

  • Our readThe page starts with the social and geographic problem before the technology, so the reader understands why faster credit processing matters.
  • Our readThe customer profile box gives industry, region, headquarters, and size, which helps a buyer quickly place the story in context.
  • Our readThe results section ties operational speed to access, contracts, funding, and rural credit, so the outcome feels broader than an IT efficiency claim.

What not to copy

Don't copy Banco da Amazônia S.A.'s Amazon-region mission, BASA Digital name, PRONAF context, or Red Hat product stack. Keep the structure of public-service problem, operational requirements, named platform build, named products, and customer-owned outcome figures.

More from Red Hat

More case studies

Steal it for your brand.

Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.