Skip to content
Alex · building Framepath@framepath
Looking for perspective

Which first step would make this easier to try?

I’m building client galleries for independent photographers. Should the first session start with an upload, or a sample gallery people can explore?

Framepath

Client galleries for independent photographers

Could a sample show the sharing flow first?

What should someone understand before uploading client work?

Illustrative conversation and fictional product.
BUILD IN PUBLIC FOR SOLO FOUNDERS

Build solo.
Think it through together.

A second perspective for your next decision.

Building a startup alone means carrying the product decisions yourself. Build in public on Buildside to explain what you are working on, ask a focused question, and exchange perspectives with other founders. Keep ownership of the decision while giving it room for discussion.

Give your question a home.

A clear founder profile and product page let new people understand the work behind your question. Explain who you are building for, what the product does, and the decision in front of you. That context makes it easier for someone to judge whether their experience is relevant.

What I’m building

Framepath

Who it serves

Independent photographers

What I’m deciding

The first-session experience

Less backstory to repeat.

Explore founder and product profiles

Two onboarding routes. One useful question.

Show a small piece of the decision instead of asking what people think of the whole startup. Give each option enough context to discuss, then ask about the task it should support. A peer can surface a blind spot; watching a photographer try the flow helps you decide what to change.

AStart with an upload

Experience the setup first.

BExplore a sample

See the sharing experience first.

Alex · building Framepath

What would a photographer need to understand before adding their own work?

Illustrative prototypes · neither option has been validated.

A check-in you can finish.

You do not need to turn every work session into content. Choose a moment when you have something specific to share, then write a short check-in. Explain what changed, where you are stuck, and the kind of response that would help. Return when you have a next step to report.

  • Share one decision.
  • Offer a useful reply on someone else’s work.
  • Come back with what you learned.
This week
What changed
I sketched two ways to start a gallery.
Where I’m stuck
I do not know what a new photographer needs to see first.
What response would help
What would you need to understand before uploading a client’s photos?

Next check:
watch a photographer
try the first session.

A simple routine for a solo founder, at your own pace.

Find a peer for this question.

Look at the work someone shares and the experience on their profile. Founder Matches and the community feed can help you explore people to connect with. A relevant exchange might be with someone who knows the workflow or someone who can question the first-time experience.

Knows the workflow

What happens between delivering a gallery and getting client approval?

FramepathFirst-session question

Sees a fresh angle

Can a new person understand the next step without your explanation?

Start with a focused exchange and agree together if you want to continue.
Explore Founder Matches

Choose what stays off the feed.

Building in public does not require sharing everything. Use sample data to explain the decision, remove identifying details, and check permissions before showing someone else’s work. You can discuss a product tradeoff without publishing client photos, private messages, credentials or sensitive business details.

Start with the question on your desk.

How can a solo founder get a useful second opinion?

Explain the user, the task and the decision, then ask a question someone can answer from relevant experience. Use the response to shape what you investigate next.

What can I share before I have customers?

Share a prototype, a design choice or an assumption you are exploring. Make the stage clear so readers can respond to the work you actually have.

Do I need to post every day?

No. Choose a pace that leaves time to build and respond. A specific question with clear context can be more useful than an update written only to fill a daily slot.

One founder. More than one perspective.

Introduce your product and the decision you are working through. Give other builders something concrete to respond to.