Building in Public8 min read

What AI Critics Taught Me About Building Upcycle

How I turned pushback into product principles.

What AI Critics Taught Me About Building Upcycle
Jason PierceFounder

A week ago, I posted about using AI to build faster. Two weeks of work: a persistent assistant, multiple websites, a SaaS product, an interactive resume, a social media calendar.

I was proud. I wanted to share.

The comments taught me something.

The Pushback

Not everyone was impressed. Some were concerned. A few were critical.

It's terrible for the planet.

Just because you're profiting doesn't make it morally justifiable.

The threshold between 'using it for convenience' and 'losing the ability to do things without it' needs to be in full view.

You seem to be diminishing concerns because other things with negative consequences already exist.

Fair points. All of them.

My first instinct was to defend. Explain. Justify.

Then I stopped. What if I listened instead?

The Reframe

I'm building Upcycle — circular economy infrastructure for Sacramento. The goal is to intercept stuff before it becomes trash and route it to its highest use. Resale. Donation. Recycling. Landfill only as a last resort.

I'm using AI to build it faster than I could alone.

But the critics weren't wrong. They were asking important questions:

These aren't obstacles to my work. They're design constraints for it.

What Changed

I went through every concern and asked: How does this shape what I'm building?

“It's terrible for the planet.”

What I'm building: Impact tracking. Every item Upcycle diverts from landfill gets measured. Every month, we'll publish net impact: tons diverted, carbon offset, environmental value created.

The goal isn't to justify AI use. The goal is to prove Upcycle is net positive. If one mattress kept out of a landfill offsets years of AI queries, show the math. Make it undeniable.

“Just because you're profiting...”

What I'm building: A transparent model. Providers earn income. Nonprofits receive donations. The community gets infrastructure. Revenue is how the system sustains itself — not the point of the system.

Revenue sustains the mission, not the point of it.

Long-term, I want Upcycle to be community-owned. A cooperative, not a startup waiting to be acquired. The people who use it should own it.

“Losing the ability to do things without it.”

What I'm building: The Upcycle Mall. A physical space with tool libraries, workshops, repair cafes, classes. A place where people build skills, not just consume services.

AI helps me build the platform faster. The Mall helps the community build capability forever. One enables the other. Neither replaces human skill — they extend it.

“You seem to be diminishing concerns.”

What I'm building: Feedback loops. The provider research survey isn't data extraction — it's relationship building. We ask before we build. We publish what we learn. We show what we changed because of what we heard.

And we go back to the critics. “You said this. We built that. What do you think now?”

The Framework

I wrote it down. A simple principle:

Every concern is a design constraint.

This isn't PR. It's not spin. It's how you build something people actually trust.

What I'm Asking Now

If you have concerns about AI, I want to hear them.

Not to argue. To understand. To build better.

This project — Upcycle — exists because I saw something broken and wanted to fix it. But I can't see everything. I need the people who push back to show me what I'm missing.

That's not weakness. That's how you build something that actually works.

The Invitation

I'm building in public. That means the wins and the criticism.

If you want to follow the journey — or contribute to it — I'm here.

Tell me what I'm missing. Show me what I should see.

I'll listen. And if you're right, you'll see it in what I build.