# \#proposal-review

**URL:** https://community.pegasy.io/tag/proposal-review/33.md

[Latest](https://community.pegasy.io/latest.md) · [Categories](https://community.pegasy.io/categories.md) · [Tags](https://community.pegasy.io/tags.md)

---

## [11 sections for a website proposal... too much?](https://community.pegasy.io/t/11-sections-for-a-website-proposal-too-much/79)

<div class="topic-metadata">

**Author:** [@signal\_form](https://community.pegasy.io/u/signal_form)\
**Replies:** 3\
**Last updated:** [July 23, 2026, 9:50am UTC](https://community.pegasy.io/t/11-sections-for-a-website-proposal-too-much/79 "2026-07-23T09:50:38Z")

</div>

I can make the flow feel clean, but 11 sections still sounds like a lot when I say it out loud :sweat\_smile: cover context goals scope process collaboration selected work timeline investment faq next steps wo…

---

## [is this scope outline clear enough?](https://community.pegasy.io/t/is-this-scope-outline-clear-enough/82)

<div class="topic-metadata">

**Author:** [@descombes\_ux](https://community.pegasy.io/u/descombes_ux)\
**Replies:** 2\
**Last updated:** [June 7, 2026, 11:40pm UTC](https://community.pegasy.io/t/is-this-scope-outline-clear-enough/82 "2026-06-07T23:40:19Z")

</div>

thinking: discovery + research flows / IA key screens design system responsive handoff would you separate research from discovery or is that overkill for the proposal?

---

## [solo freelancer: team section yes or no?](https://community.pegasy.io/t/solo-freelancer-team-section-yes-or-no/81)

<div class="topic-metadata">

**Author:** [@nami\_digital\_studio](https://community.pegasy.io/u/nami_digital_studio)\
**Replies:** 2\
**Last updated:** [May 27, 2026, 3:05am UTC](https://community.pegasy.io/t/solo-freelancer-team-section-yes-or-no/81 "2026-05-27T03:05:36Z")

</div>

feels weird adding a ‘team’ section when the team is literally me lol. do you just skip it or make it more about how you work / collaborators?

---

## [selected work before scope or after?](https://community.pegasy.io/t/selected-work-before-scope-or-after/80)

<div class="topic-metadata">

**Author:** [@honaker\_creative](https://community.pegasy.io/u/honaker_creative)\
**Replies:** 2\
**Last updated:** [April 28, 2026, 11:39pm UTC](https://community.pegasy.io/t/selected-work-before-scope-or-after/80 "2026-04-28T23:39:46Z")

</div>

for a branding proposal, where do you like showing work? part of me wants proof early. other part says let them understand the project first.

---

## [video proposal feels long. would you keep the full process?](https://community.pegasy.io/t/video-proposal-feels-long-would-you-keep-the-full-process/78)

<div class="topic-metadata">

**Author:** [@hiromu\_filmworks](https://community.pegasy.io/u/hiromu_filmworks)\
**Replies:** 3\
**Last updated:** [February 3, 2026, 9:36am UTC](https://community.pegasy.io/t/video-proposal-feels-long-would-you-keep-the-full-process/78 "2026-02-03T09:36:18Z")

</div>

working on a pretty straightforward film proposal. right now its: brief / direction deliverables pre-prod shoot post usage pricing starting to feel a bit long. would you keep the full process or compress it?

---

## [does a branding proposal need a big 'strategy' section every time?](https://community.pegasy.io/t/does-a-branding-proposal-need-a-big-strategy-section-every-time/83)

<div class="topic-metadata">

**Author:** [@office\_stojanovic](https://community.pegasy.io/u/office_stojanovic)\
**Replies:** 2\
**Last updated:** [December 6, 2025, 7:11pm UTC](https://community.pegasy.io/t/does-a-branding-proposal-need-a-big-strategy-section-every-time/83 "2025-12-06T19:11:24Z")

</div>

sometimes the job is honestly just identity execution from an already solid brief. feels wrong forcing a huge strategy section in there just because branding proposals usually have one.