Big Pixel

09/02/2026

In this episode of Biz/Dev, we sit down with Page Conway, Founder and CEO of Ensembled, to talk about what it takes to build a marketplace when you truly understand the people you’re building it for.

Page shares her experience tackling the challenges of a two-sided market, understanding CAC, vibe coding her app, and why trust and security matter when your entire business is built around community.

https://www.thebigpixel.net/podcasts/the-business-of-borrowing-w-page-conway

09/01/2026

When did you last get an update on a build without asking for it first?

For a lot of clients the honest answer is the demo before launch, which is a long stretch to spend wondering whether the thing is on track.

What you should be getting from a development partner:

✅ A written update every week on a schedule
✅ A fixed fee, so scope conversations happen before invoices do
✅ Access to the working build itself
✅ A named person who answers when something looks wrong
✅ A list of what was tested before you were asked to review

We run weekly communication and fixed-fee delivery, and clients stay with us for years because they always know where a project stands.

Look at your last three status updates and check who started each one.

https://thebigpixel.net/contact-us

09/01/2026

The new Biz/Dev episode is live!

This week, we sit down with Page Conway, Founder and CEO of Ensembled, to talk about what happens when a founder knows her market firsthand and builds around a problem she’s seen play out in real life.

We get into:

✅ Turning existing customer behavior into a business opportunity
✅ Building for a specific community instead of trying to serve everyone
✅ Learning directly from your earliest users
✅ Making smart decisions about where and how to grow
✅ What it takes to turn an idea into a product people actually use

🎧 Catch the full conversation with Page: https://www.thebigpixel.net/podcast

08/31/2026

Tomorrow on Biz/Dev, we sit down with Page Conway, Founder and CEO of Ensembled, to talk about building and growing a marketplace designed specifically for sorority communities.

We get into:

✅ The challenges of building a two-sided marketplace
✅ Knowing your customer and understanding CAC
✅ Building trust and security into a community-based platform
✅ Vibe coding an app from the ground up
✅ Testing, learning, and making decisions as an early-stage founder

🎧 Page’s episode goes live tomorrow: https://www.thebigpixel.net/podcast

08/31/2026

What are repeated tickets actually telling you?

Where the software made someone ask for help it should have handed them.

Most repeated tickets translate cleanly into a specific system gap:

"Where is my status?" usually means the portal does not show enough progress, timing, or ownership.

"How do I do this?" usually means the interface does not match how people actually think about the task.

"Can you change this for me?" usually means users lack the permissions or self-service to do it themselves.

"This number is wrong" usually means the data definitions or their source are not visible.

"I already sent that" usually means a handoff between two systems is broken.

Every one of those is a product or workflow question that happens to arrive through the support inbox.

And they are not free to answer.

FULL ARTICLE: https://www.thebigpixel.net/articles/are-your-support-tickets-actually-product-requirements

08/28/2026

Did you catch this week’s Biz/Dev episode with Michael Linnane, Founder and CEO of FeedStation?

We talked e-commerce, customer behavior, technology, and what it takes to create better buying experiences online.

There’s a lot to take away from the conversation, and Michael wraps it up with a few of his top tips for business owners and builders.

🎧 Catch the full episode, and don’t miss Michael’s top tips to close out the week: https://www.thebigpixel.net/podcasts/rev-your-engines-w-michael-linnane

08/27/2026

At Biz/Dev, we believe the best conversations happen when people are willing to get into the questions that really matter.

We bring together founders, business owners, and leaders to share what they’ve learned, challenge conventional thinking, and have the conversations that usually happen behind closed doors.

No gatekeeping.

Real experiences.

Hard-earned lessons.

Honest conversations about leadership, technology, growth, and everything that comes with building a business.

We ask the tough questions.

We dig deep.

We go where other business podcasts simply won’t.

Because some questions are just too important to leave unanswered.

https://www.thebigpixel.net/podcast

08/26/2026

Count how many times you say "and then you just click here" in your next demo.

Training is what a team does to compensate for a screen that will not explain itself, and that cost repeats with every new hire and every new customer.

What a UX audit looks for:

🧪Where people hesitate before clicking
🧪Which screens generate support questions
🧪What your team explains in every demo
🧪Where users abandon a task partway through
🧪Which features exist and go unused

We redesigned the marketplace experience for Gopher around how people move through it, and design and development sit on the same team here, which keeps the built version faithful to the designed one.

Watch one new user work for an hour without helping them, and write down every place they stop.

On-Demand Community Marketplace | UI and UX redesign to improve clarity, reduce friction, and create a more polished app experience.

08/26/2026

Technology shapes far more than the products we build.

It changes how people work, communicate, make decisions, and solve problems. That makes the thinking behind what we create just as important as the technology itself.

The best ideas come from understanding the people involved, asking better questions, and collaborating across perspectives before jumping to a solution.

Michael Linnane brings a thoughtful perspective to what it means to build responsibly in a world increasingly driven by technology.

🎙️ Catch the full conversation on this week’s Biz/Dev: https://www.thebigpixel.net/podcasts/rev-your-engines-w-michael-linnane

08/25/2026

Customers who call right after reading your portal are telling you the screen answered the wrong question.

It reported a status when they wanted to know what happens next.

A completed action should leave the person clear on:

✅What happened
✅What it means for them
✅Who owns the next step
✅When to expect movement
✅What to do if it looks wrong

We start portal projects in the support queue, because the questions your team answers over and over already describe which screens need work.

The fix is often a few fields and an afternoon of copywriting, which is why this work tends to cost less than clients expect.

Sort last month's tickets by what the person was actually asking rather than by product area.

https://www.thebigpixel.net/design -audit