Marcos
Ondruska.

Find your next move.

13 destinations

PointYieldFlagship systemTOMObservation researchThe LabAll toolsApproachWorking principlesContactStart a conversationRound RobinSchedulingTennis TrackerMatch reviewTennis Tracker V2Match intelligenceMortgage CalculatorPlanningCar Loan CalculatorPlanningAsteroidsPlayGalaga-Style ShooterPlaySports Stroke FormVideo review

Tab to explore. Esc to close. Ctrl / Cmd + K to open.

INDEPENDENT BUILDER / PRODUCT & SYSTEMS

A FIELD OF POSSIBILITIES / 001

Complex systems.Clear decisions.

Connected possibilities. An orbital form inspired by PointYield.

I'm Marcos Ondruska. I build tools that make the important part easier to see, from points and travel to the patterns inside a tennis match.

Explore the work
THREE DIRECTIONS.
ONE WAY OF THINKING.01 / DECISION ENGINEPointYield 02 / OBSERVATION SYSTEMTOM 03 / TOOLS & EXPERIMENTSThe Lab

SELECTED WORK / 01

Live flagship

PointYield

Credit. Points. Travel.
One connected decision.

Not another feed.
A reason to act.

PointYield is a closed-loop decision engine for credit, points, and travel. It helps the user decide when to earn, transfer, hold, or book by turning fragmented loyalty data into verified opportunities.

Points strategy is usually scattered across loyalty accounts, transfer math, and award searches. The hard part is knowing what is real, what it is worth, and what deserves action.

Try the decision study

INTERACTIVE EXHIBIT
Illustrative inputs. A real design principle.

PointYield / Decision studyDemo data
01 / THE INPUT

Connect the fragments.

Points, a possible award route, and travel dates. Useful inputs, but not yet a reason to act.

Illustrative workflow. No live searches or bookings.

THE CLOSED LOOP

Earn / Transfer / Hold / Book

Different actions.
The same demand for evidence.
01What it does

It connects credit cards, loyalty programs, transfer paths, award availability, and redemption value inside one working decision surface. Truth layer, interface, and next best action are designed together.

02Why it is nontrivial

The engine has to verify opportunity, compare value across programs, preserve context, and surface a next best action without collapsing into a feed or generic assistant. Keep evidence beside the action, not just a compelling number.

03The evidence boundary

Missing proof is not availability. The interactive study demonstrates that principle without making a live provider request. The loyalty picture stays intact until the user can see what is available, what it is worth, and what to do next.

04Interface studies
PointYield interface illustration: Points, value, and action
Points, value, and actionInterface illustration, not live state.
PointYield interface illustration: Award availability, transfer paths, and redemption value
Award availability, transfer paths, and redemption valueInterface illustration, not live state.
PointYield interface illustration: Earn, transfer, hold, or book
Earn, transfer, hold, or bookInterface illustration, not live state.

SELECTED WORK / 02

Research / in development

TOM

First, observe.
Then, understand.

OBSERVATION / 001Concept illustration
01 HIT02 BOUNCE03 HIT
Visual input Event ledger Match context

FROM MOTION TO MEANING

01Hit.A moment of contact.
02Bounce.A fact worth keeping.
03Context.The structure of a rally.

Conceptual sequence, not live analysis.

Before the insight,
get the observation right.

TOM is a deterministic tennis observation system. It turns tennis video into an auditable event ledger built around hits, bounces, and rally structure.

Its job is observation to truth: convert noisy visual input into match facts that analytics and downstream decision systems can trust. The architecture is being developed to generalize beyond tennis.

This is the architecture being explored, not a live video-analysis demo. The public surface stays restrained while the system is in development.

Try local video annotation

SELECTED WORK / 03

Explore all 8 tools

Serious tools.
Room to play.

Schedulers, trackers, calculators, and side builds stay available in the Lab. They matter because they were used, not because they round out a portfolio.

Find something useful.08 APPS

THE PERSON BEHIND THE SYSTEMS

The court.
The code.
The same instinct.

You have to see what matters, make a decision, and learn from what happens next. That is the thread connecting the work here.

Marcos OndruskaProduct thinking. Systems building. Tennis.

The work is product judgment applied to messy systems. Keep what is true, decide what matters first, and make the result legible to the person using it.

01

Structure before polish

If the underlying model is loose, better visuals only hide the problem. The system gets settled before the styling.

02

Truth before comfort

The interface should tell the truth even when the truth is inconvenient. Confidence, ambiguity, and change need to show up cleanly.

03

One view can carry more

The goal is not panel sprawl. The goal is a view that keeps truth, context, and next best action close together.

04

Use decides what survives

I keep the work that stays useful after the first demo. Everything else is noise.

HAVE SOMETHING WORTH MAKING CLEAR?

Open to a small number of product
and systems conversations.

Let's make
the next move.

If the problem is technically messy, decision-heavy, and needs a better interface than the category usually gets, reach out.

marcosondruska@gmail.com