What Makes a Deal Worth It? by Jack

What Makes a Deal Worth It? by Jack - October 2026 Scholarship Essay

The question that changed how I think about learning didn’t come from a classroom. It came from a garage full of things I had bought to resell and couldn’t move.

I started reselling in high school, flipping items I found on Facebook Marketplace, at local sales, and on eBay. At first my method was simple: if I could buy something for less than it seemed to sell for online, I bought it. Some flips went great. Others sat for weeks, and when they finally sold, fees and shipping ate most of the profit. I couldn’t explain why one deal worked and another didn’t. That bothered me more than losing the money did, and it turned into a real question: what actually makes a deal worth buying?

I started treating my reselling like an experiment. For every item, I tracked what I paid, what similar items had actually sold for (not just what people were asking), how long it took to sell, and what I kept after fees and shipping. Patterns showed up quickly. The gap between buy price and listing price, which was the only thing I had been looking at, turned out to be one of the weakest predictors of a good flip. Sold prices told a very different story than asking prices, because plenty of listings sit unsold at prices nobody will pay. How fast a category sold mattered almost as much as the margin, because money tied up in slow inventory is money I couldn’t use on the next deal. Condition, local demand, and the season all shifted the results in ways I wouldn’t have guessed.

Once I understood the problem, I wanted to solve it for more than just myself. Other resellers dealing in high-priced items were making the same mistakes I had, so I set out to build a tool that would find and filter deals using the factors that actually mattered. That decision pulled me into a subject I had barely touched before: software development. I taught myself React to build the interface and Supabase to store and organize the data, and I set up Stripe so it could work as a membership service. I called the project FlipKnowledge.

Building it was humbling. My first database design was messy, and I had to rebuild it once I understood how the data actually needed to connect. Features that seemed simple in my head took days to get working. I learned to debug by isolating one piece at a time instead of changing five things and hoping, which is basically the scientific method applied to code. Every bug was a small hypothesis I had to test. The site isn’t running right now, but taking it from an idea to a working product taught me more than any finished result could have.

The biggest thing this project taught me is that a good question is worth more than a quick answer. When I only asked “can I sell this for more than I paid?” I got shallow results. When I asked “what really determines whether a deal succeeds?” I had to gather evidence, question my assumptions, and accept that my first instinct was often wrong. That shift, from guessing to testing, is the most valuable thing I’ve learned, and it applies far beyond reselling.

It also showed me what I want to study. I started out curious about money and ended up fascinated by data and the systems that organize it. That curiosity is a big reason I’m now pursuing Information Technology at Central Connecticut State University. I want to understand the systems I’ve been teaching myself to build, in more depth and with better methods, and I want to keep asking better questions.

What began as a frustrating pile of unsold items became the project that showed me how I learn best: by being curious about a real problem, testing my ideas, and building something from what I find.