ProSwag / Fusion BrandsJoshuaCohen.net

Optional appendix

Estimated build hours.

This is supporting detail for the proposal. The prices, payment terms, timing and included work are stated in the main proposal.

These estimates describe the complete tools using the early version already started. They are not a record of time already spent. We use them to agree the deliverables and completion checks for the $2,500 trial; the full three-tool project remains the separate $6,000 option.

Hours appendix 1 of 5

Software 1 of 3: Mockup tool build hours

18–30 estimated additional hours

These are planning estimates, not hours already worked, guaranteed maximums or a delivery date. They include building, human review, testing, corrections and handover.

Estimated work by feature or phase
WorkHours
Agree the staff task, examples and final check2–3
Improve mockup comparison, logo placement and changes6–10
Add supplied product materials and save chosen versions2–4
Check the tool still works after changes, including retries and phone-sized screens4–7
Write instructions and hand over the tool2–3
Allow time to fix problems and make focused improvements2–3

For comparison, similar work started from scratch is estimated at 55–90 hours. Those hours are not added to the work or charged on top when the existing code is reused.

Hours appendix 2 of 5

Software 2 of 3: Catalog tool build hours

24–40 estimated additional hours

These are planning estimates, not hours already worked, guaranteed maximums or a delivery date. They include building, human review, testing, corrections and handover.

The 20-entry example uses finished supplied images and reliable details and prices. It is not 20 custom branded mockups or a permanent limit on later use. The starting tool still needs changes and testing for this example.

Estimated work by feature or phase
WorkHours
Agree catalog fields, layout and final check2–4
Separate catalog entries from chosen mockups; improve adding data, prices and the reusable layout10–16
Prepare and check the 20 supplied catalog entries4–7
Check saving, reopening, reordering, reuse, phone-sized screens and output4–6
Write instructions and hand over the tool2–3
Allow time to fix problems and make focused improvements2–4

For comparison, similar work started from scratch is estimated at 60–95 hours. Those hours are not added to the work or charged on top when the existing code is reused.

Hours appendix 3 of 5

Software 3 of 3: Customer link build hours

18–30 estimated additional hours

These are planning estimates, not hours already worked, guaranteed maximums or a delivery date. They include building, human review, testing, corrections and handover.

Estimated work by feature or phase
WorkHours
Agree input materials, public sharing and the recipient check2–3
Build the reusable page and a reviewed copy of the catalog6–10
Publish approved pages and keep each published version clear2–4
Check the link on a phone outside the office, private-data exclusions and older versions4–6
Write instructions and hand over the tool2–3
Allow time to fix problems and make focused improvements2–4

For comparison, similar work started from scratch is estimated at 35–55 hours. Those hours are not added to the work or charged on top when the existing code is reused.

Hours appendix 4 of 5

All three tools, sharing the same starting work

49–80 estimated additional hours

These are planning estimates, not hours already worked, guaranteed maximums or a delivery date. They include building, human review, testing, corrections and handover.

This is an alternative combined estimate. Shared work is counted once; do not add the three individual tool totals to it. It covers staff tools used on a computer and separately approved public customer pages, not a protected online service for staff.

Estimated work by feature or phase
WorkHours
Agree the work, materials and final checks3–5
Prepare the existing code and shared product information4–6
Improve the mockup tool6–10
Build catalog collections, prices and a reusable layout10–16
Prepare view-only customer pages and publish approved versions6–10
Prepare and check the 20 supplied catalog entries4–7
Check the tools work together and customers receive the right page7–11
Demonstrate the work and hand it over3–5
Allow time to fix problems and improve the result6–10

Hours appendix 5 of 5

Assumptions and checks.

These estimates assume one developer who knows the starting code, usable product photos and logos, reliable details and prices, and timely decisions. The proposal website is not the software being offered.

The catalog estimate includes 4–7 hours to prepare and check 20 supplied product or color entries. Missing data, new artwork or unusual placements may change the work. We confirm that before changing the agreed price or dates.

Each individual tool estimate includes the starting work, planning, testing and handover it needs. These complete-tool estimates help us agree the $2,500 trial package; they do not set a fixed number of included apps or an hourly allowance. The trial deliverables and checks are agreed in writing based on realistic effort within the two-week plan. The $6,000 full-project price is also separate from these hour estimates.

The customer-page estimate assumes an approved place to publish simple public pages. It includes keeping the approved images with the right page, leaving out private contacts and internal notes, and removing staff approval or editing controls. The current staff preview cannot simply be put online unchanged.

The customer-page tool can use supplied catalog information without buying the catalog editor. Private online hosting, staff or customer sign-ins, customer uploads and AI image generation need separate estimates.

Confidence is low to moderate until we try the selected work with real materials. Time spent waiting for feedback, access or approval may extend the calendar. Confirm the work, dates and any changes before approval.