Peer-to-peer buying and selling for AMA members, built on the Phase 1 platform and matched to the Exchange mobile scope.
Phase 1 put AMA services on the Exchange. Phase 2 adds the product marketplace on web: members list items, find them nearby, talk to each other, and meet safely to complete the exchange. The scope follows the three epics in AMA's Exchange scope, so web and mobile ship the same experience. This proposal covers design, development, QA and project management for all 29 features as one project.
A peer-to-peer marketplace lives or dies on its first transactions. Sellers will not list where nobody is browsing, and buyers will not come back to an empty or risky feed. We sequence the build so each epic removes the next barrier to a completed exchange.
The minimum loop for a sale: create a listing, get found through search, filters and the map, then close the deal in a chat tied to that listing.
AMA's structural advantage. A trusted brand, physical centres as safe exchange zones and verified members give AMA an edge that open classifieds cannot match.
Reasons to come back: saved listings, alerts for new matches and messages, and a personal dashboard that turns one-time sellers into repeat members.
Every feature below is in scope for responsive web. Features marked Custom design are not yet defined in the mobile designs, so their final shape is set with your team during design.
Real-time chat between buyer and seller, tied to each listing, with up to five attachments per message. When a listing is sold or closed, the chat becomes read-only and the history stays visible.
An inbox split into Buying and Selling tabs, each with its own unread count.
Upload photos from the device, reorder them and choose the cover photo. Photo count and size limits confirmed in design.
Refinements to the listing creation flow, shaped with your team during design.
A toggle on the listing, shown as a badge and usable as a search filter. The negotiation itself happens in chat.
Category and condition as structured listing fields, searchable alongside the title.
Search filters for price range, category, condition and the other attributes in the designs, plus sorting.
Sold, Reserved, Closed and Archived statuses, set by the seller. Closed and archived listings drop out of search.
A radius control in search, starting from the member's location, that limits results to that distance.
Search results on a map, plus a Near me button that uses the browser's location.
Guests can browse and search. Any action, such as chatting, saving a favourite or listing an item, asks them to sign in.
A profile page with photo, name and the details in the designs, with profile editing.
A required confirmation, tied to the terms, that the member owns the item. The time of acceptance is stored.
On publish, the member's active listings are checked for a matching title and photos, and the duplicate is blocked or flagged. Matching rules agreed in design.
Hints inside the listing form, plus a page on how to list well and what items are prohibited.
Before publishing, the title and description are screened by automated content moderation and a banned-phrase list. A match shows a clear error in the form.
Admins can ban a member from the admin console. A banned member sees a message and cannot post or chat.
Safety tips shown inside the chat and on the sale page, before members meet.
Admins add, edit and remove safe exchange locations such as AMA centres. Members see the nearest ones on a map and can share one in the chat.
Once a listing is marked sold, buyer and seller rate each other from 1 to 5 stars with a comment. The average shows on the profile.
Members can verify their identity and earn a Verified badge on their profile. The verification method is confirmed with AMA before build.
A notification when a favourited listing is reserved or sold.
Members save search criteria and choose a daily or weekly digest of new listings that match.
A notification for new chat messages, throttled so a busy conversation does not flood the member's inbox.
The listing form saves a draft as the member fills it in, so they can finish later.
A heart on listing cards and a Favourites page. Sold or removed listings stay in the list with their status.
New listings wait in Pending until approved, and the seller can see the status.
A member home for their listings, chats, favourites and alerts. Contents defined with your team during design.
Members recommend a seller to other members. The mechanics are defined and designed with AMA as part of this phase.
Paige leads web design. The Exchange mobile designs are the starting point, so members get the same patterns on any device, and we only design from scratch where a feature has no mobile reference yet.
Translate the app screens for home, search, listing creation, listing states, messages, profile and listing view into responsive web layouts, using the Phase 1 design system.
Custom design for the personalized dashboard, referrals, listing creation improvements, the Safe Exchange Zone admin and alert settings.
Each epic's designs are reviewed and signed off by AMA before development starts on it, so build time is spent on agreed screens.
These keep the scope and the investment honest. Anything outside them is handled through a change request, the same way we work today.
Design starts first and stays one epic ahead of development. Each epic is demoed as it completes, then the full release goes through QA and AMA user acceptance testing. Week numbers count from kickoff and are indicative.
The investment covers the full Phase 2 scope above as a single project. The range reflects the four custom-design features, which are not yet defined. We confirm the final fee within the range once their designs are approved.
A deposit to start, equal monthly payments across the three months of the project, and a holdback released when AMA signs off user acceptance testing.
The deposit is set on the low end of the range. Once the final fee is confirmed at design sign-off, the monthly payments absorb the difference. Amounts above are in CAD before GST. 5% GST is not included in the quote and is added to each invoice. Work outside this scope, or changes after design sign-off, is estimated and approved separately as a change request.
Check each feature description against what your team expects, and flag anything missing or misread.
Settle ID verification, web notification channels, photo limits and duplicate rules, so design starts with clear answers.
We turn this proposal into the contract for Phase 2 and hold a start date.
Paige begins with Epic 0 screens, and development follows as each epic is approved.
Reply with questions or edits to the scope, and we will lock the open points together.
dcody@marketplacestudio.io