Selected work / jua.ai

jua.ai

<a href="https://jua.ai/" target="_blank" rel="noopener noreferrer">jua.ai</a> builds products on top of weather models. We worked directly with founder Marvin Gabler and built the first working version: a usable interface for forecasts, maps, charts, alerts, customer access, and the infrastructure behind it. That early version helped jua.ai move toward first customers and supported the story around a ~$2.5M round

Round

~$2.5M

Product

Forecasts · maps · alerts

Stack

Web · API · AWS

jua.ai

Web app, forecast interface, interactive maps, charts, alerts, authentication, API access, and AWS infrastructure.

What we built

A working web product for forecasts: map, charts, alerts, login, customer access, and API-backed infrastructure.

What mattered

The complex technology had to feel simple to use: not an internal tool, but a polished interface for people.

What changed

jua.ai had a first version that could be opened, understood, tested, and used in early customer workflows.

Case study

jua.ai

<a href="https://jua.ai/" target="_blank" rel="noopener noreferrer">jua.ai</a> builds products on top of weather models. We helped turn a strong technical foundation into the first working web version: an interface where users choose an area on a map, read a forecast, compare signals, and set alerts without relying on internal tools. We worked directly with founder Marvin Gabler. The result was a product that looked and behaved like a real first version, not an internal prototype. It helped jua.ai move toward first customers and supported the story around a funding round of about $2.5M.

Challenge

A strong model needs a clear interface

jua.ai had a serious technical foundation. But users judge the product by how quickly they understand it: which area they are looking at, what the forecast says, where the signals change, and which alerts they can configure. The job was clarity. The map, charts, states, alerts, access, and infrastructure needed to work as one product.

Solution

A web product for forecasts and alerts

We built the first version as one product, not a set of technical pages. Maps, forecasts, charts, and alerts had to feel connected and guide the user without extra explanation. A user could choose an area, read the forecast, understand the movement, and set monitoring in the same interface. Behind that simplicity was the heavy product work: API integration, auth, customer access, notifications, deployment, and AWS infrastructure.

Technical work

The interface and the system behind it

The hardest part was making a live technical system feel simple from the outside. Forecast APIs, map behavior, chart data, alert logic, authentication, and deployment all had to line up. When one layer works separately, the product quickly becomes heavy. We helped connect those parts into the first product foundation: web app, forecast integration, alerts, auth, controlled access, AWS deployment, and a clear release process.

Turning complex technology into a clear product?

We help teams turn models, data, and infrastructure into a web product where interface, backend, access, and deployment work together.

View
Brief (optional)