Our story

We tried to fix returns. Here's what happened.

Return Done started in Chicago in 2023, after we noticed how complicated everyday retail returns had become.

What began as an idea between four graduate students turned into a working product that we tested with customers around the Illinois Tech community. We built the platform, put up posters around campus, scheduled real pickups, and learned firsthand that solving the software problem was only one part of building a logistics company.

The original experiment ended once we saw how operationally intensive last-mile returns could be. The problem itself never went away. Returns are still fragmented, still slow, and still an errand nobody wants.

This site is a modern rebuild of that original product, and an exploration of what Return Done could look like today.

The journey

  1. The itch

    Four graduate students in Chicago noticed how much effort a simple return took: labels, boxes, a trip across town, a line, and then weeks of checking for the refund.

  2. Building it

    We designed and built the first version ourselves: a return request form, pickup scheduling with two-hour windows, online payment, confirmation emails and an operations inbox for every request.

  3. Going to campus

    We put up posters around the Illinois Tech campus and signed up our first customers: students juggling classes, assignments and return deadlines.

  4. Real pickups

    We scheduled real doorstep pickups, checked items at the door, packed and labeled them, and took them back to the retailer.

  5. Pausing

    The software held up. The operations were the hard part. We chose not to keep scaling it with a team of four.

  6. 2026 rebuild

    A modern rebuild of the original product, exploring what Return Done could look like with today's tools.

What we learned

Building software is different from building operations

The booking flow was the part we knew how to build. Getting the right item, from the right door, to the right counter, every time, was the real work.

Logistics runs on physical-world constraints

Traffic, buzzers, store hours, carrier cut-offs and people who aren't home. None of it shows up in a database schema.

Early customer validation matters

A poster and a simple form taught us more than any planning document. The interest was real. The open question was what it cost to serve it.

Product simplicity often hides operational complexity

“We'll pick it up” is three words for the customer and a routing, timing and verification problem for the team behind it.

Built from zero

Return Done was designed and engineered from the ground up, spanning the customer experience, return workflows, scheduling, product architecture and early operational experiments. The 2026 rebuild keeps the original business rules, like two-hour pickup windows and Saturday Return Day pricing, and rebuilds everything around them.

View the source
How the stack changed from 2023 to 2026
Area20232026
FrontendCreate React App, Bootstrap, jQueryNext.js App Router, React 19, strict TypeScript
DesignAd-hoc SCSS per componentToken-based design system with CSS Modules
BackendASP.NET Core 6 email API on AzureTyped route handlers with shared zod validation
Return dataForm data emailed to an ops inboxTyped return records with a status lifecycle
TrackingEmail updatesLive timeline and a returns dashboard
NewNoneSmart Return Assistant with an optional LLM and a deterministic fallback

The team

Gita Disale

Co-Founder & CTO

Co-founded Return Done and led the technology: built the original product and helped define how pickups and returns actually ran. Return Done was a four-person founding team.

See what the rebuilt product feels like.

Schedule a ReturnExplore Demo Account