Why we built Abistu

We built Abistu because visual work often needs a private, simple, structured way to receive a client response.

As a professional photographer, I often had work that was not on a public website, not meant for a public portfolio, and not convenient to send as a loose folder. My wife and I kept returning to the same practical situation: a client asks for a specific kind of image, we know we have a selection, but we need a clean way to show it privately and receive a precise answer.

The answer might be: this photograph in this size, this one on matte paper, this one framed, these three as a set, and a question about whether a custom format is possible. That answer should not be scattered across screenshots, filenames, chat messages, and memory. It should come back as one clear request.

Abistu is a simple private gallery for visual selections. You create a gallery, upload a set of images or visual items, send one private link, and let the client choose what they need.

The important part is not only showing the images. The important part is the response. The client can select one item or many items, leave comments on specific selections, add one general message, and submit their contact details.

For the owner, this means the response arrives in a usable form. Instead of rebuilding the client’s decision from a conversation, the owner receives selected items, item comments, a general request, contact details, and a shared request reference.

The problem appeared in a very ordinary way. Someone asks whether we have more photographs of a certain model, a certain mood, a certain location, a black-and-white street set, a quiet studio set, or a group of images that belong together but are not published on the public site.

A public website is not the right place for every selection. Some work is private. Some work is experimental. Some work is only relevant to one client. Some work is part of a larger archive, grouped by subject, model, theme, print possibility, or visual direction.

The usual options were never quite right. A folder can deliver files, but it does not collect a clean decision. A public portfolio shows finished work, but it is not built for private client selection. A chat is fast, but comments and choices quickly become messy. Screenshots work for a moment, then become confusing later.

The real pain is not sending images. The real pain is receiving the answer in a way that can be used for actual work.

The workflow we wanted was deliberately simple.

First, create a private gallery for a specific purpose: a model selection, a print selection, a themed set, a group of unpublished work, a small catalogue of available pieces, or a custom set prepared for one client.

Second, upload the images or visual items. The gallery does not have to be a public portfolio. It can be temporary, private, practical, and focused on the decision the client needs to make.

Third, send one private link. The client opens it in a browser, without needing an account. They review the work, select the pieces they want, leave comments where needed, add a general note, and submit the request.

Finally, the owner receives a structured request instead of a messy thread. The client’s decision stays connected to the visual work.

From the client’s side, the experience should feel almost obvious.

They open a private link. They see a clean gallery. They do not have to install anything, create an account, or learn a complicated interface.

If they want a photograph, they select it. If they want a certain print size, they write it next to that image. If they want matte paper, a frame, a custom crop, a set of several images, or a question about a specific piece, they can write that where it belongs.

They can also add one general message for the whole request. That message might explain the project, the delivery deadline, the room where the print will hang, the intended gift, the preferred material, or any other context that does not belong to only one image.

The goal is not to make the client do more work. The goal is to let the client answer in the same visual context where the decision is being made.

The owner receives a clear request that can be acted on.

Instead of trying to match screenshots to original files, decode filenames from a chat, or remember which message was final, the owner sees the selected items and the comments attached to those items.

This matters for photography, but the same pattern appears in many types of visual work. The owner may need to prepare prints, quote prices, answer questions, check availability, produce a custom size, or continue a conversation with confidence.

When the answer is structured, the next step becomes easier. The owner does not have to spend time asking what the client meant. The request already contains the pieces needed to continue.

One detail became important very quickly: both sides should be able to keep the same record.

The owner can receive the request by email, and the client can receive an email copy of the same submitted request. Both sides can refer to the same selected items, the same comments, the same general message, and the same request reference number.

This is useful because a visual decision often becomes part of a longer conversation. A client may come back later. A print detail may need confirmation. A custom format may need a price. A group of images may become an order, a proposal, or a follow-up selection.

When both sides have the same request record, the conversation does not restart from memory. It starts from the same submitted request.

Abistu was not built to replace every tool. It was built for a narrower job: private visual review with a clear response.

That difference is the reason Abistu exists. The centre of the product is not only presentation. It is the return path: the client’s response.

Use Abistu when you have visual work that a client needs to review privately.

It is especially useful when the set is not meant for a public site, when several similar options need to be compared, when each item may need a separate comment, or when the next step depends on exactly what the client chooses.

For a photographer, that might mean private print selections, unpublished work, model-specific sets, black-and-white groups, archive selections, or custom visual proposals.

For other visual businesses, the same idea can apply to cakes, flowers, interior materials, design options, architecture visuals, styling sets, handmade items, products, and references.

The common situation is simple: you need to show visual options and receive a clear answer.

A private gallery is not necessary for every exchange.

If you only need to deliver final files, a storage folder may be enough. If you only want to show your best public work, a portfolio page is better. If the client needs to pay immediately for standard products, a shop may be the right format.

If the decision is not visual, a form, email, or document may be more appropriate.

Abistu is most useful when the visual context matters. If the client’s answer needs to stay attached to specific images or items, the private gallery becomes much more valuable.

• — A photography client asks whether there are more images from a certain model. A private gallery can show a focused set without publishing it on the main website.
• — A collector asks for black-and-white street photographs. The photographer sends a private selection and receives comments about size, paper, framing, and custom format questions.
• — A client wants several prints but needs to compare options first. They select favourites and write notes next to each image.
• — A cake maker sends visual references so the client can choose a direction and comment on colours, size, and occasion.
• — A florist sends bouquet ideas. The client marks favourites and explains changes without sending cropped screenshots.
• — An interior designer sends material options. The client chooses a direction and leaves comments in one place.
• — An architect sends several visual directions for a presentation. The client selects one and adds notes for changes.
• — A stylist sends outfit options. The client can accept, reject, and comment item by item.

Different professions, same pattern: visual options go out, a clear response needs to come back.

Abistu was built from the practical side of visual work.

The first question was not how to create another beautiful portfolio. The question was how to make the answer usable after the client has seen the work.

That is why the product is intentionally simple. A private gallery. One link. Selected items. Item comments. One general message. Contact details. Email copies. A shared request reference.

This structure keeps the client experience light while giving the owner a response that can actually be used.

For us, that was the missing piece. We did not need a heavier public platform. We needed a practical bridge between a private visual selection and the next real step in the work.

The easiest way to understand Abistu is to try the flow.

Open the demo gallery, select one or several items, leave a note, add a general message, and submit a test request.

The point is not only to see how the gallery looks. The point is to feel the difference between sending visual work and receiving a clear client answer.