Together PRD

PRD for together.ng

By ·

Together.ng — Product Requirements & Implementation Plan

Document type: Product Requirements Document (PRD) / Functional Implementation Plan Product: Together Working domain: together.ng Status: Detailed product specification Scope: Product behavior, workflows, business rules, functional requirements, and acceptance criteria Explicitly excluded for now: Technology choices, system architecture, infrastructure, implementation code, matching algorithms, AI implementation, and detailed data schemas Vision Document: Together Vision


1. Purpose of This Document

This document describes how Together should function as a complete product.

It is intentionally written independently of technology and implementation architecture. A product manager, designer, engineer, QA engineer, or future technical team should be able to read it and understand:

The objective is to define the behavior of the product before deciding how it will be built.


2. Product Definition

Together is a non-monetary network that connects people who need help becoming more capable with people who can contribute knowledge, skills, resources, access, time, or experience.

The platform does not require reciprocal exchange.

A person can receive help without giving anything back.

A person can contribute without expecting anything in return.

A person may participate entirely as a recipient, entirely as a contributor, or move between both roles.

The core product loop is:

Need → Request → Discovery/Matching → Contribution → Outcome → Trust → Future Contribution

3. Product Goals

3.1 Primary goals

Together should:

  1. Make it easy and dignified to ask for productive help.
  2. Help users formulate specific, actionable requests.
  3. Connect needs with people who may be able to help.
  4. Allow people to discover worthwhile needs even when they were not specifically matched.
  5. Make contribution simple and rewarding without turning it into a monetary system.
  6. Build trust through observable contribution history rather than popularity.
  7. Enable safe sharing of physical resources.
  8. Encourage people who receive help to eventually become contributors when they are able.
  9. Make useful human capability easier to discover.
  10. Create a sustainable community culture centered around learning, building, creating, and progressing.

3.2 Secondary goals

Together should eventually:


4. Non-Goals

The initial product should not become:

Monetary transactions between users are outside the core Together model.


5. Core Product Principles

5.1 Asking for help is acceptable

A user does not need to demonstrate usefulness before asking for help.

There must be no public indicator that implies a person is less valuable because they have helped nobody.

5.2 Contribution is voluntary

A user may receive help without subsequently contributing.

Together can encourage contribution but should not create debt.

5.3 Help should increase capability

The platform should favor needs involving:

5.4 Trust should describe behavior

Trust indicators should answer:

“Has this person historically been reliable?”

They should not answer:

“How popular is this person?”

5.5 Accessibility before complexity

Anyone should be able to participate in low-risk activities without completing extensive verification.

Additional requirements can be introduced when an activity creates additional risk.

5.6 Human dignity

The product language should avoid terms and interaction patterns associated with begging, charity ranking, pity, or social inferiority.


6. User Types

These are participation roles rather than permanent account types.

6.1 Recipient

A person currently asking for help.

Examples:

6.2 Contributor

A person offering help.

Examples:

6.3 Supporter

A user who helps indirectly.

Examples:

A user can occupy all three roles.


7. Account Creation and Onboarding

7.1 Registration

A new user creates an account using the supported registration method.

The registration process should collect only information necessary for normal participation.

The user should be introduced to Together's philosophy during onboarding.

The product should explicitly communicate:

You can ask for help even if you currently have nothing to offer.

This is important because the onboarding experience establishes the culture of the platform.

7.2 Basic profile

The user can provide:

A user should not be required to complete every section.

7.3 Contribution capabilities

The user can select one or more predefined categories.

Examples:

The taxonomy should be designed to evolve.

Within a category, the user can specify individual capabilities.

Example:

Technology

7.4 Contribution availability

Where relevant, the user can indicate:

7.5 No-contribution onboarding

If a user selects no contribution categories, onboarding still completes normally.

The product should reinforce:

“That's okay. You can simply use Together when you need help.”

No negative score, warning, or shame indicator should be displayed.


8. User Profile

A profile should represent a person's participation and trust rather than function as a conventional social-media profile.

8.1 Profile information

A profile may display:

8.2 What should not be central

The profile should not emphasize:

8.3 Privacy

Users should control what personal information is publicly visible.

Exact addresses should never be publicly exposed for resource exchanges.

Exact contact information should remain private unless users choose to share it through the appropriate interaction.


9. Creating a Request for Help

Creating a request is one of the most important workflows in Together.

9.1 Start request

The user selects:

Ask for help

The application explains that a specific request is more likely to receive useful responses.

9.2 Select category

The user selects the most relevant category.

The user should be able to search categories if the list is large.

The application should allow a request to be classified into the most appropriate category rather than requiring users to understand the full taxonomy.

9.3 Describe the goal

The user explains what they are trying to accomplish.

Example:

“I am trying to learn electronics and build my first simple circuit.”

9.4 Describe the barrier

The user explains what is preventing progress.

Example:

“I understand the theory but don't have anyone experienced who can guide me through practical work.”

9.5 Describe the requested help

The user states what would help.

Example:

“I need someone experienced with basic electronics who can answer questions and guide me through my first project.”

The user should not have to know the exact resource needed. Together should allow people to describe the problem and let potential contributors suggest appropriate forms of help.

9.6 Optional request details

Depending on category, the request may ask for:

Only relevant questions should be shown.

9.7 Request preview

Before publishing, the user sees the complete request and can edit it.

The application should highlight missing information that may reduce the likelihood of receiving help.

9.8 Publishing

The user publishes the request.

Once published:


10. Request Quality Guidance

Together should actively improve requests rather than merely reject poorly written ones.

A user who writes:

“I need a laptop.”

should receive guidance such as:

“What are you trying to do with the laptop?”

The goal is not to interrogate the user.

The application should progressively help them provide useful context.

A high-quality request should make it easy for someone to answer:

  1. What does this person want to accomplish?
  2. Why are they currently blocked?
  3. What kind of help would move them forward?
  4. What constraints matter?
  5. Where and when is the help needed?

11. Request States

A request should have an explicit lifecycle.

Recommended states:

  1. Draft
  2. Published
  3. Receiving responses
  4. Help arranged
  5. In progress
  6. Completed
  7. Closed
  8. Cancelled
  9. Archived
  10. Under review, when moderation is required

The user should be able to understand the current state at all times.


12. Request Discovery

Users should be able to discover needs without receiving a direct match.

12.1 General featured feed

The featured area displays requests that the community may find worthwhile.

The feed should prioritize useful discovery rather than simply displaying the newest posts.

12.2 Category feeds

Each category has its own request feed.

For example:

12.3 Search

Users can search requests using natural descriptions and structured categories.

Search should support finding both:

12.4 Filters

Potential filters include:


13. Voting

Any eligible user can upvote a request they believe deserves attention.

An upvote means:

“I think this need is worthwhile and should receive visibility.”

It does not mean:

A user should be able to remove their vote.

The application should prevent repeated voting intended to artificially inflate visibility.


14. Sharing Requests

Users should be able to share requests externally.

The shared representation should contain enough context for someone to understand the need and return to Together.

Sharing is another discovery mechanism.

A person who cannot help may know someone who can.


15. Matching

Together should maintain a relationship between requests and potentially relevant contributors.

Matching should consider information such as:

A match does not automatically mean the contributor has agreed to help.

It means:

This request appears relevant to what this person said they may be able to contribute.

The user should remain in control of whether to respond.


16. Contributor Notifications

When a new request appears to match a user's stated capabilities, the user may receive a notification.

Notifications should explain why the request is relevant.

Example:

“Someone is looking for help with beginner Python. You indicated that you can help with Python.”

Users should be able to control:

The goal is to avoid notification fatigue.


17. Responding to a Request

A potential contributor selects:

I can help

They should be able to explain how they can help.

Example:

“I can help you with the first three weeks of the course. I'm available online on Saturday afternoons.”

The contributor should not have to commit to the entire request.

They may offer a narrower form of assistance.


18. Multiple Contributors

A request can receive multiple offers.

The requester should be able to:

The system should not assume the first response is automatically the best response.


19. Communication

Once a contributor and requester decide to proceed, Together should provide a communication channel.

Communication should support:

Users should not be forced to publicly expose personal contact details.


20. Completing a Contribution

After the help takes place, the contribution should be marked as completed.

Either participant can initiate completion.

The other participant can confirm.

A completed contribution should record enough information to establish that the interaction occurred without unnecessarily exposing private conversation details.


21. Outcome Confirmation

The recipient should be asked:

Did this help you move forward?

Possible responses:

The recipient can optionally explain what happened.

This feedback should be more important than simple likes.

The objective is to determine whether Together is actually helping people progress.


22. Contributor Feedback

The recipient can provide structured feedback about the contribution.

Potential dimensions:

This information contributes to trust signals.

It should not become a public star-rating competition.


23. Reputation

Reputation is accumulated from meaningful participation.

Potential reputation signals:

A reputation indicator should never represent a monetary balance.

There should be no concept of:

“You have 50 points and therefore can request 50 units of help.”

24. Verified Skills

A skill can become verified through meaningful evidence.

Possible evidence sources include:

Verification should communicate:

“There is evidence that this person can help with this skill.”

It should not imply professional licensing unless the relevant credential has actually been verified.


25. Badges

Badges may recognize contribution patterns.

Examples:

Badges should be descriptive and celebratory.

They should not provide economic value or unlock unfair social status.

Badges should not be required for participation.


26. Contribution Without Reciprocity

After a user receives help, Together may encourage them to contribute when they are able.

For example:

“Glad you got the help you needed. Is there anything you know or have that someone else might find useful?”

This should be an invitation, not an obligation.

There should be no countdown, debt, or expectation that the person must give back.


27. Resource Sharing

Together supports sharing of physical and digital resources.

Resource types can include:

The contributor specifies whether the resource is:


28. Lending Workflow

Physical lending requires additional safeguards.

Step 1 — Resource listing

The owner describes:

Step 2 — Request

A user asks to borrow it and explains the intended use.

Step 3 — Trust assessment

Depending on resource value and risk, Together may require additional verification or an established history of successful participation.

Step 4 — Agreement

Both parties confirm:

Step 5 — Condition record

The owner records the item's condition using descriptions and, where appropriate, photographs.

The borrower acknowledges the condition.

Step 6 — Handoff

Both parties confirm that the resource was handed over.

Step 7 — Return

The borrower returns the resource.

The return condition is recorded.

Step 8 — Confirmation

The owner confirms whether the resource was returned satisfactorily.

Step 9 — Contribution history

A successful lending interaction becomes part of the relevant trust history.


29. High-Value Resource Rules

High-value resources should not be treated like books.

The platform may require:

New users should not automatically gain access to high-value resources.

The exact thresholds can be determined during implementation based on real-world usage and risk.


30. Resource Damage or Loss

If an item is returned damaged, lost, or not returned:

  1. The owner reports the issue.
  2. The borrower is notified.
  3. Both parties can provide relevant information.
  4. The existing condition and lending records are reviewed.
  5. The issue can enter a dispute process.
  6. Together may restrict one or both accounts while investigating.
  7. Serious violations can result in suspension or permanent removal.
  8. Where appropriate and legally necessary, relevant information can be provided to authorities.

Together should not automatically decide every dispute in favor of the owner or borrower.

The objective is fair handling based on available evidence.


31. Repeat Abuse and New Accounts

Reputation alone cannot prevent someone from abandoning an account and creating another.

Together should therefore treat trust as more than a public profile metric.

High-risk activities can require stronger account verification.

New accounts should have limited access to activities where misuse could cause substantial loss.

The platform should detect and restrict suspicious patterns where possible.

The product should prioritize:

Preventing a new account from immediately gaining access to high-risk resources

rather than attempting to make it impossible for anyone to ever create multiple accounts.


32. Insurance

Insurance is not part of the basic Together experience.

It may eventually be offered through external partnerships for high-value physical resources.

Potential future options:

Together should not assume responsibility for insuring all resources itself.

This feature should only be introduced if real usage demonstrates a need.


33. Institutions

Organizations should eventually be able to participate.

Potential institutions include:

They may contribute:

Institutional accounts should have appropriate verification and administrative capabilities.


34. Moderation

Together needs moderation because not every request or interaction will be appropriate.

Moderation should address:

Moderation should distinguish between:

A person asking for help

and:

A person abusing the platform.

Need alone should never be treated as evidence of wrongdoing.


35. Reporting

Users should be able to report:

A report should allow the user to select a reason and optionally provide context.

The reporter should not be publicly identified to the reported user unless there is a legitimate reason.


36. Safety Rules

The platform should have clear rules covering:

The platform should not imply professional guarantees where contributors are simply community members.


37. Notifications

Notifications should exist for meaningful events.

Potential notifications include:

Requester

Contributor

Community

Users should be able to control notification frequency and categories.


38. Following Needs Without Building a Follower Culture

Users may want to follow a request or topic so they can return later.

This should be treated as following a need, not following a person.

The product should avoid turning this into a social follower graph.

Examples:

Follow this request
Follow Technology needs
Follow Book requests

These relationships exist for discovery and participation, not social status.


39. Request Closure

A requester can close a request when:

The closure reason can be recorded.

If help was received, the requester should be encouraged to confirm the outcome.

Closed requests remain useful as historical contribution records unless removed for privacy, safety, or moderation reasons.


40. Unsuccessful Requests

Not every request will receive help.

A request can remain open for an appropriate period.

The application may periodically ask:

“Do you still need help with this?”

The user can:

The platform should not imply that failure to receive help means the request was invalid or the requester was undeserving.


41. Request Editing

A requester should be able to edit an open request.

Significant changes should be visible to people who have already responded when necessary.

If the fundamental need changes, the application may suggest creating a new request instead.


42. Duplicate and Related Requests

The same need may be posted by multiple people.

Together should make it possible to identify related requests.

Related requests may eventually help users discover:

This creates a path from individual requests toward reusable community knowledge.


43. Community Knowledge

When a particular need repeatedly appears, Together should eventually be able to surface accumulated knowledge around it.

For example:

“How do I learn electronics?”

could lead to:

The platform can gradually transform repeated human interactions into discoverable knowledge.


44. AI-Assisted Product Experiences

AI implementation is intentionally outside the current technical scope, but the product should reserve functional opportunities for future automation.

Potential experiences include:

These capabilities should assist coordination rather than replace human contribution.


45. Search and Discovery of Contributors

A requester should eventually be able to discover people who may help.

A contributor profile should show relevant capability and trust information.

The requester should not need to know the person's name.

They should be able to search by:

The system should prioritize relevant capability rather than popularity.


46. Local Versus Remote Help

Every relevant request should distinguish between forms of help.

Examples:

Remote

Local

Either

Location should only be required when it materially affects the request.


47. User Privacy

Together should collect and expose information according to the minimum needed for successful coordination.

Public profiles should not reveal:

Physical exchanges may require users to exchange additional information privately after choosing to proceed.


48. Blocking

Users should be able to block another user.

Blocking should prevent unwanted interaction according to the applicable product rules.

A blocked user should not be able to use ordinary platform features to repeatedly contact the blocker.

Blocking should not remove legitimate safety-reporting capabilities.


49. Trust and Safety Escalation

Trust issues should have levels.

Low-level issue

Example:

Potential response:

Moderate issue

Example:

Potential response:

Serious issue

Example:

Potential response:


50. Admin Functions

Administrators should be able to:

Administrative actions should be auditable.


51. Category Management

Categories should not be permanently fixed.

Administrators should be able to:

Changes should avoid destroying historical records.


52. Request Quality and Moderation Are Different

A request can be poorly written without being inappropriate.

For example:

“Need a computer to learn coding.”

This is a low-quality request but not necessarily a moderation problem.

The application should first attempt to help the user improve it.

Moderation should be reserved for requests that violate platform rules.

This distinction is important to maintaining a welcoming culture.


53. Abuse of Voting

Voting should not become a mechanism for manipulation.

The product should detect or restrict:

Voting should affect discovery but should not determine whether someone deserves help.


54. Success Metrics

Primary metric

Successful contributions

A successful contribution is an interaction where:

  1. A meaningful need is identified.
  2. Someone offers help.
  3. The help is arranged.
  4. The contribution occurs.
  5. The recipient confirms that it helped them move forward.

Supporting metrics

Track:


55. Core User Journeys

Journey A — New user needs help

  1. User registers.
  2. User sees that having nothing to contribute is acceptable.
  3. User selects Ask for Help.
  4. User selects a category.
  5. User describes their goal.
  6. User explains their barrier.
  7. Together guides them toward a specific request.
  8. User provides relevant constraints.
  9. User publishes the request.
  10. Potential contributors receive relevant notifications.
  11. Other users discover and upvote the request.
  12. Contributors respond.
  13. User evaluates responses.
  14. User accepts help.
  15. Communication begins.
  16. Help takes place.
  17. Contribution is marked complete.
  18. User confirms whether it helped.
  19. Contributor's successful contribution history is updated.
  20. User is later invited—but not required—to contribute something themselves.

Journey B — User wants to help generally

  1. User opens featured needs.
  2. User browses requests.
  3. User filters by category if desired.
  4. User finds a request they can help with.
  5. User opens it.
  6. User selects I Can Help.
  7. User describes their proposed contribution.
  8. Requester receives the response.
  9. Requester accepts or declines.
  10. Communication occurs.
  11. Help is delivered.
  12. Both parties confirm completion.
  13. Recipient confirms outcome.
  14. Contributor receives appropriate trust/reputation credit.

Journey C — User sees a need they cannot solve

  1. User discovers a request.
  2. User cannot personally provide the requested help.
  3. User upvotes the request.
  4. Optionally, user shares it.
  5. The request receives additional visibility.
  6. Another person discovers it and contributes.

Journey D — User lends a book

  1. User lists a book as available to lend.
  2. Another user finds the resource.
  3. Borrower explains intended use.
  4. Owner reviews the request.
  5. Both agree to the lending period.
  6. Condition is documented.
  7. Handoff is confirmed.
  8. Borrower uses the book.
  9. Book is returned.
  10. Condition is confirmed.
  11. Lending interaction is recorded as successful.

Journey E — High-value resource lending

  1. Owner lists a valuable resource.
  2. Borrower requests it.
  3. Together determines that stronger trust requirements apply.
  4. Borrower completes required verification.
  5. Borrower's eligibility is established.
  6. Owner reviews borrower information.
  7. Both agree to terms.
  8. Condition is documented.
  9. Handoff is confirmed.
  10. Resource is returned.
  11. Condition is checked.
  12. Any issue is either closed successfully or escalated into dispute handling.
  13. Successful completion contributes to future trust.

56. Acceptance Criteria for the MVP

The MVP should not be considered functionally complete until a user can perform the complete core loop.

Account

Requests

Discovery

Matching

Contributions

Reputation

Safety


57. Detailed Testing Strategy

The product should be tested as complete user journeys rather than only isolated screens.

57.1 Registration tests

Verify:

57.2 Request tests

Verify:

57.3 Discovery tests

Verify:

57.4 Matching tests

Verify:

57.5 Contribution tests

Verify:

57.6 Reputation tests

Verify:

57.7 Lending tests

Verify:

57.8 Safety tests

Verify:


58. Edge Cases

The implementation should explicitly account for:

Each case should have a defined user-facing outcome and administrative behavior.


59. Product Language

Language is part of the product's identity.

Prefer:

Avoid language that implies:

Examples of language to avoid:


60. MVP Scope

The first version should focus on validating the central behavior.

Include

Carefully limited

These should be implemented conservatively because they create significant trust and operational complexity.

Defer


61. Phased Product Development

Phase 1 — Core community loop

Validate:

Ask → Match → Help → Confirm

Features:

Phase 2 — Better trust and resource sharing

Validate:

People can safely share tangible resources.

Features:

Phase 3 — Network expansion

Expand from individuals to:

Phase 4 — Intelligent coordination

Introduce automation to:


62. The Most Important Product Loop to Validate

Before building the full platform, the most important question is:

Will strangers actually help strangers with productive needs when money is deliberately removed from the interaction?

The MVP should therefore optimize for learning this.

A successful early community should demonstrate examples such as:

Person A asks for help learning something.
Person B sees the request.
Person B offers help.
Person A progresses.
The interaction is confirmed.

Then:

Person A eventually becomes Person C's helper.

If that loop happens naturally, Together has evidence that its core social model works.


63. Product North Star

Together should ultimately make this statement true:

If there is something useful a person needs to learn, build, create, or accomplish, there is a reasonable chance that Together can connect them with someone who can help.

And equally:

If someone has knowledge, skills, resources, experience, or access they are willing to share, Together should make it easier for the people who need it to find them.

The product succeeds when these two capabilities increasingly connect.


64. Final Product Philosophy

Together is not trying to eliminate people's needs.

It is trying to eliminate the unnecessary barriers between people and the people who can help them overcome those barriers.

The platform should make asking easier.

It should make contributing easier.

It should make useful needs easier to discover.

It should make trustworthy contributors easier to identify.

It should make dormant resources easier to put to productive use.

And it should create a culture where receiving help is not a position of weakness and giving help is not a transaction.

The fundamental relationship remains:

I can help you.
You can help someone else.
Together, we can all become more capable.

← Back to blog