Client proposal image project: what to plan
Plan a client proposal image project with clear source files, editable layers, review checkpoints, and exports sized for easy approval.
A proposal image can look polished and still miss the brief. The crop may hide an important detail, the text may be hard to read at presentation size, or the client may not know what they are being asked to approve.
Plan the image around the decision your client needs to make. The Photo Editor gives you layers, selections, brushes, text, adjustments, and filters to build a clear visual without mixing every change into one flat edit.
Build the image project in a clear order
- Start in the Photo Editor with a copy of the source photo. Before editing, write down the proposal's purpose, who will view it, and what you need the client to approve. Keep the original file in a separate folder so you can return to it if a review changes direction.
- Choose one main message for the image. Decide whether it should show a finished concept, compare two options, explain a proposed change, or support a cost or schedule discussion. A single image that tries to answer every question can become difficult to scan.
- Compose around the subject and leave room for any labels or callouts. Crop away distractions, but keep the context the client needs to judge the proposal. If text or a logo is part of the design, check that it does not cover a key feature.
- Separate different kinds of edits into layers. Keep the source image separate from added text, shapes, or touch-ups. Layers make later changes easier because you can adjust one part without repainting the whole image.
- Review the design at the size where the client will see it. Check the image on a presentation screen or in the document where it will appear. Then export a delivery copy in the format and dimensions the client requested, while keeping the source photo separate.
Before sharing, open the exported copy and make sure it displays as expected. A correct-looking edit in the editor is not enough if the exported file is cropped, hard to read, or saved in the wrong format.
Choose an image treatment that fits the proposal
Use a clean photo when realism matters
For a product, space, or installation proposal, the client may need to judge real materials and proportions. Keep color and lighting adjustments restrained so the image remains a credible reference. If you make a substantial visual change, label it as a concept rather than presenting it as a photograph of an existing result.
Add labels when the client needs to compare details
Text and simple visual marks can direct attention to a feature, location, or proposed change. Keep labels short and use a consistent style. Make sure each label points clearly to the relevant area, and do not place important text too close to the edge where it could be cut off in a slide or printed page.
Use a comparison when the choice is the point
If the proposal presents two directions, show them at comparable sizes and with similar framing. A dramatic crop or stronger contrast on only one option can make the comparison feel unfair. Add a brief identifier to each version so the client can refer to them in feedback.
Keep layers while changes are still likely
Layered work is useful during review because text, retouching, and other changes can be adjusted separately. A flattened image is simpler to share, but it is harder to revise. Keep your editable working version separate from the exported image you send for approval.
Prevent avoidable revisions
- Confirm the delivery requirements. Ask for the intended placement, image dimensions, file format, and any brand or accessibility requirements before designing. A proposal slide, a printed handout, and a web preview may need different crops or text sizes.
- Check rights and permissions. Use images you own, have permission to use, or are otherwise cleared for the proposal. If the photo includes a person, private workspace, address, or customer information, confirm that it is appropriate to share with the intended audience.
- Keep the original and working copy distinct. Duplicate the source before editing, and give versions clear names such as
concept-a-reviewandconcept-a-approved. Avoid overwriting the original or relying on a file name likefinal-finalto track approval status. - Make the visual hierarchy obvious. The proposed idea should stand out before supporting details. Use size, placement, and contrast consistently. If every label, border, and decorative element competes for attention, remove anything that does not help the client understand the decision.
- Ask for focused feedback. Present a specific question, such as whether the client prefers one of two layouts or whether a marked feature is in the right location. This is more useful than asking for general reactions after sending several unrelated versions.
- Check the exported file, not just the editor view. Verify the crop, text legibility, and colors in the saved copy. If it will be placed in a slide deck or document, check it in that context too, because the final display size can make small labels unreadable.
Keep the review copy easy to understand
Give the client enough context to review the image without making them guess. Use a short filename and, when needed, include a brief note that identifies what is proposed and what feedback you want. Mark a mockup clearly if it shows an unbuilt design or an edited scene. That prevents a visual concept from being mistaken for a photo of completed work.
For multiple options, keep the differences deliberate. If one version changes the crop and another changes the color treatment, the client may not know which difference they are evaluating. Compare like with like, or explain the separate decisions in the note that accompanies the files.
The Photo Editor runs in your browser, and photos and files stay on your device while you work.
