# How IOMETE challenged hackCBS 9.0 builders to make complex tech easier to buy

A technically strong product can still be difficult to choose. The person evaluating it needs to understand what it does, where it fits, what it changes, and how to explain that decision to everyone else involved. For complex data infrastructure, those questions can be as demanding as the engineering itself.

At **hackCBS 9.0**, IOMETE supported a sponsor challenge with a deceptively simple brief: **“Make Complex Tech Easy to Buy.”** It asked builders to think about how people discover, understand, and choose complex technology. The track offered **mechanical keyboards to the top two winning teams**. Across the weekend of 31 October and 1 November 2026, it gave hackers a problem that sits at the intersection of engineering, product experience, and communication.

![IOMETE challenge brief presented at hackCBS 9.0](https://cdn.hashnode.com/uploads/covers/6399d0692f612d4e4a766bad/de9525d7-eb58-4ee4-960e-6423fd4ae3f2.jpg align="center")

## Why technical buying gets complicated

A platform decision rarely belongs to one person. A data engineer wants to know whether existing pipelines will work. An architect looks at deployment and integration. A security team asks where data lives and who controls access. A business sponsor wants to understand the outcome and the cost. Each person is evaluating the same product through a different lens.

[IOMETE](https://iomete.com/) is a useful example of that challenge. It is a self-hosted data lakehouse built around Apache Iceberg, Apache Spark, and Kubernetes. Organizations can run it in their own environment, including on-premises or in cloud infrastructure they control. Those architectural choices matter to teams dealing with data ownership, governance, and scale. They also take more than a feature list to explain well.

Imagine an evaluator trying to make the case internally. A statement such as “sovereign data platform” may catch their attention, but the next conversation is more concrete: Where does the data sit? Which parts run in our infrastructure? How will existing tools connect? What happens to permissions, operations, and cost? If the answers are scattered across pages, diagrams, and sales calls, even an interested team can struggle to move forward.

That is why **making complex technology understandable is part of the product experience**. A clear explanation helps people test whether a platform actually fits their needs. It gives an internal champion something accurate to take into the next meeting and gives decision makers a way to examine the tradeoffs.

## What a good answer to the challenge might look like

The IOMETE brief left room for different approaches. A builder could imagine an interactive architecture walkthrough that shows how data flows through a platform. Another could create a guided evaluation that changes its explanation for an engineer, a security reviewer, or a finance lead. A third might turn dense documentation into a set of grounded answers with links to the underlying evidence.

The details would matter. A useful tool should let someone inspect a claim, see the assumptions behind a recommendation, and understand where a proposed solution may be a poor fit. It should reduce the work of evaluating a product without hiding the technical choices. For an enterprise purchase, that kind of clarity can be more valuable than another polished feature carousel.

A hackathon is a good place to explore the idea. Builders have limited time, so they have to decide which part of the journey is most confusing and make one improvement tangible. A prototype might focus on the first five minutes of discovery, the handoff from an engineer to a decision maker, or the moment a team compares deployment options. Each is a small slice of a much larger buying process, but a good slice can reveal where people get stuck.

![A hackCBS builder working on a laptop during the event](https://cdn.hashnode.com/uploads/covers/6399d0692f612d4e4a766bad/5baef8e9-8fdb-4804-86d2-ae04acd07227.jpg align="center")

## Celebrating the builders

**Team BaseCase** and **Team Coffee Please** were recognized in the **IOMETE sponsor track**. BaseCase brought together Ajitesh Vishwakarma, Anurag Jaiswal, Shivani Nayak, and Sejal Choudhary. Coffee Please included Arkin Kansra, Khushi Bhaskar, Prapti Gupta, and Yash Mishra.

![Team BaseCase and Team Coffee Please recognized in the IOMETE track](https://cdn.hashnode.com/uploads/covers/6399d0692f612d4e4a766bad/b751c47c-0aee-483a-8610-248c798995f2.jpg align="center")

Congratulations to both teams. We hope they keep developing their ideas and sharing what they learned from building under a tight deadline.

## Beyond a weekend prototype

The bigger question behind this track remains useful after the hackathon: **Can the next person understand the technology well enough to make a sound decision?** A strong product story should let people move from an appealing promise to a concrete evaluation. It should make architecture, deployment, and tradeoffs easier to inspect and discuss.

Thank you to IOMETE for supporting hackCBS 9.0 and giving builders a challenge rooted in a real problem that technical teams face. And thank you to the hackers who spent the weekend building, testing, and presenting their ideas.

To learn more about the platform behind the challenge, explore [IOMETE's data lakehouse](https://iomete.com/product/data-platform/platform-overview).
