Project Requirements & Execution Plan

Table Of Contents

●​ INTENTION

●​ SERVICE PROVIDER OVERVIEW

●​ CUSTOMER OVERVIEW

●​ PROJECT BASIC DETAILS

●​ PRD GIVEN BY CUSTOMER

●​ COMPREHENSIVE PRD BY ZEPUL

●​ MVP REQUIREMENTS, COVERED FEATURES

●​ ADDITIONAL FEATURES, MISSING OR LESS DETAILED

●​ TECHNICAL CONSIDERATIONS

●​ ROADMAP AND PHASED DEVELOPMENT

●​ RISKS AND DEPENDENCIES

●​ SUCCESS AND CRITERIA METRICS

●​ ESSENTIALS FOR MVP

●​ RESOURCE ALLOCATION

●​ TIMELINES AND MILESTONES

●​ CONCLUSION

INTENTION​
​
The purpose of this document is to outline the PRD provided by the client and list MVP requirements,
technical considerations, technical and operational suggestions, resource allocation, and a clear
roadmap for project completion.

SERVICE PROVIDER OVERVIEW

Name of the Organization -

Industry -
Headquarters - Hyderabad, Telangana
Founded -
Certifications -

CUSTOMER OVERVIEW

Private & Confidential www.zepul.com

Name of the Organization - Zepul Private Limited
Industry - Technology | HRTech | Artificial Intelligence | Human Resources Services
Headquarters - Hyderabad, Telangana
Founded - 2022
Certifications - DPIIT Startup India Certified, MSME Udyam Certified

PROJECT BASIC DETAILS

Project Code Name - TOS E2E INDIA

Client Location - India & USA
Application Launch Location - India Sub Continent

BASIC PR FOR UNDERSTANDING

User Login/Registration

●​ Account access through OTP sent to user supplied phone numbers or email. User profile
created and maintained using the phone number or email ID.
●​ Terms and conditions: Setting out the rules and regulations for website
usage

Features for Users ​

●​ Ability to like, comment, and share the stories.

●​ Ability to bookmark news articles
●​ Ability to personalize a page to view their bookmarks
●​ Separate tags for politics, finance, sports and more. ​

Features for Admins/Content Creators

●​ Dashboard for metrics - day/week/month-wise stats on Story views

●​ Personalized access to the dashboard for Super
admins/admins/editors The dashboard should display direct links
to the latest/trending news Story view language preference -
Telugu, English & Hindi
●​ Story writing and editing language preference - Telugu and English
●​ Story sharing—The initial link sharing must only contain the primary side perspective;
users should only be able to view the dual perspective of a story upon opening the
link.
●​ Having sentiment meter with highest votes having Green color and other side with Red
color.

COMPREHENSIVE PRD BY ZEPUL (Including suggestions)

Product Overview
A news aggregation and commentary application that presents curated stories from various
sources. The unique selling proposition (USP) is to provide side-by-side “Right” and “Left”
perspectives for each story, along with a “Full Coverage” mode that allows deeper exploration.

Primary Goals

●​ Aggregation of News: Provide a single platform to read headlines and

in-depth articles from multiple sources.
●​ Perspective View: Show contrasting (political/ideological) viewpoints side-by-side.
●​ Increased Engagement: Allow users to like, comment, bookmark, and share articles.

Private & Confidential www.zepul.com

 ●​ Admin & Editor Management: Simplify content uploads, editorial curation, and
performance tracking.

Scope & Objectives

MVP (Initial Release)

●​ User Registration & Profile Management
●​ Basic News Feed (with categories and two perspectives)
●​ Engagement Features (like, comment, share, bookmark)
●​ Editor Dashboard for Story Creation & Management
●​ Admin Dashboard for Analytics
●​ Automatic ingestion of news from RSS or partner feeds
●​ Sentiment Meter indicating user preference for either perspective

Post-MVP & Long-Term

●​ Advanced personalizations (AI-based recommended stories, topic-based
preferences, push notifications)
●​ Extended coverage (more languages, deeper category structure)
●​ Rich editorial workflows (version control, scheduling, moderation)
●​ Monetization (advertising modules, subscription tiers)
STAKE HOLDER & ROLES

Product Manager
Defines product vision and requirements, prioritizes features, coordinates with stakeholders.

Tech Lead/Engineering Team

Architecture and development of front end, back end, content ingestion pipelines, and
integrations.

Design & UX Team

Creates user flows, wireframes, and final visual designs to ensure a cohesive user
experience.

Editors & Content Creators

Write and/or curate news articles, fact-check, schedule content, manage categories and
tags.

Admins / Super Admins

Oversee the entire platform, manage user privileges, track analytics, handle
escalations, and moderate content.

End Users
Consume news content, engage with likes, comments, shares; personalize feeds and
manage bookmarks.

USER PERSONAS & SCENARIOS

Casual News Reader

Motivations: Wants quick headlines, easy consumption, diverse viewpoints in one place.

Actions: Reads trending news, occasionally bookmarks, might share stories to social
media/WhatsApp.
Politically Engaged Reader
Motivations: Enjoys in-depth coverage, demands multiple perspectives to form balanced

Private & Confidential www.zepul.com

opinions.

Actions: Frequently visits for nuanced news coverage, comments on stories, uses the “Full
Coverage” button.

Editor / Content Creator

Motivations: Wants an intuitive editorial tool, easy story creation, ability to track performance.

Actions: Logs into the Editor Dashboard, uploads or edits stories, tracks how stories perform.

Admin / Super Admin

Motivations: Needs a macro view of the platform’s performance, user engagement,
and overall content quality.

Actions: Monitors stats (views, likes, shares), manages user roles, oversees platform
health.

MVP REQUIREMENTS ( COVERED FEATURES)

User Registration & Profiles

1.Sign-Up/Log-In via Phone or Email

●​ Flow: User enters phone/email → receives OTP → verifies → account created.
●​ Persist: Store minimal user info (name, phone/email, accepted T&Cs).

2. Terms and Conditions

●​ T&Cs must be presented during sign-up, covering acceptable use, content rights,
privacy, disclaimers.

Core User Features

1. News Feed with Categories

●​ Default categories: Politics, Finance, Sports, Entertainment, Technology.
●​ Users can scroll through or filter by category.

2.Two Perspectives Display

●​ Each story page shows either a “Right” and “Left” perspective side-by-side or a
“Primary” perspective with a toggle to reveal the second.
●​ “Full Coverage” button to see other sources covering the same story.

3. Like, Comment & Share

●​ Like: Tally up user sentiments.
●​ Comment: Basic text comments with potential moderation
●​ Share: Generates a link that shows a teaser (one perspective). Clicking leads to the
full dual-perspective view in the app or on the website.

4. Bookmark / My Bookmarks
●​ Users can save stories for later reading.
●​ Access under a “Bookmarks” or “Saved” tab.

5. Story View Language Preference

●​ Users can switch between Telugu, English, and Hindi if those translations or
versions are available.

Admin / Editor Features

Private & Confidential www.zepul.com

1. Admin Dashboard
●​ Metrics: day/week/month stats on story views, likes, shares, comments. o
Top/Trending news list.

2. Role-Based Access
●​ Super Admin: Manage the platform, user roles, site settings.
●​ Admin: Manage content, moderate comments.
●​ Editor: Create, edit, publish stories, limited stats view.

3. Story Writing & Editing

●​ Compose stories in Telugu or English. (Extend to Hindi as needed.)
●​ Add tags, categories, metadata (e.g., source, “right” or “left” orientation).

4. Sentiment Meter
●​ Real-time bar or pie chart showing user engagement or voting on each
perspective.
●​ Green color for higher user preference, Red for the lesser.

5. Story Sharing Restrictions

●​ The shared link only shows the primary side. A full dual-perspective view is only
visible upon visiting the app or the site.

News Ingestion & Content Extraction

Goal: Pull in news automatically while still allowing manual editorial submissions

1.Direct Feeds / RSS Feeds

●​ Implementation: Use a background job (e.g., cron, serverless function) that fetches
RSS feeds from partner publishers every 15–30 minutes.
●​ Pros: Easy integration, standardized data format (XML/JSON).
●​ Cons: May not always get full text.

2.Content Aggregation API’s

●​ Examples: NewsAPI, RapidAPI, or other licensed aggregator.
●​ Pros: Single integration for multiple sources.
●​ Cons: Potential subscription costs, usage limits, partial coverage.

ADDITIONAL ( MISSING OR LESS DETAILED)

Below are features either not specified in detail or missing from the original MVP outline

1.Editorial Workflows
●​ Version Control: Track changes made by editors; revert if needed.
●​ Approval/Scheduling: A content approval flow for sensitive stories, schedule
publication times.
●​ QC/Pre-Publish Checks: Spell checks, format checks, compliance.

2. Comment Moderation / Community Management

●​ Moderation Tools: Flag or remove inappropriate comments.

●​ Filtered Comments: Automatic detection of spam, profanity, hate speech using NLP if
feasible.
●​ User Reporting: Mechanism for users to report harassment or misinformation.
3. Push Notifications

Private & Confidential www.zepul.com

 ●​ Breaking News Alerts: Users get immediate push notifications for major news stories.
●​ Personalized Notifications: AI-based or preference-based recommended stories.

4. Advanced Personalization (AI/ML)

●​ Recommendation Engine: Machine learning to suggest stories based on user reading
habits, location, or preferences.
●​ Topic Clustering: Group related articles into “Full Coverage” clusters. • Perspective
Classification: Automated identification of “Right” vs. “Left” leaning based on NLP
analysis.

5. Search & Discovery

●​ Search: By keywords, hashtags, date, or publisher.
●​ Filters: By category, language, date range, or perspective.

6. Accessibility & Localization

●​ Font Size Adjustments: Make it easier for visually impaired or older users.
●​ Text-to-Speech: Potentially for visually impaired.
●​ Multiple Regional Languages: Beyond Telugu, English, Hindi, possibly add more in the
future.

7. Performance & Scalability

●​ Caching (CDN): Store frequently accessed news or assets for fast delivery.
●​ Microservices Architecture: If anticipating large-scale traffic or complex integrations.
●​ Load Balancing: Handle traffic spikes during breaking news or major events.

8. Analytics & Reporting

●​ Real-Time Analytics: Number of unique visitors, sessions, bounce rate, dwell time.
●​ User Behavior: Track scroll depth, click patterns for UI/UX improvements.
●​ Content Performance: Which categories, authors, or perspective angles drive the
most engagement.

TECHNICAL CONSIDERATIONS

1. Front End
●​ Tech Stack: React for a responsive web. Native mobile (Android/iOS) or hybrid
frameworks (React Native) for app.
●​ UI/UX: Must be designed for quick readability, minimal friction for sign-up.

2. Back End
●​ Language: Node.js
●​ Database: SQL (MySQL/Postgres) or NoSQL (MongoDB) depending on structure.
●​ APIs: REST for feeding the front end with aggregated news data.

3. Hosting & Infrastructure

●​ Cloud-based (AWS, Azure, GCP).
●​ CI/CD: Automated build/deploy pipeline.
●​ Security: SSL/TLS encryption, robust user authentication, role-based access. 4. Logging &
Error Handling
●​ Centralized logging for error detection and performance monitoring. o Crash analytics,
user event tracking.

ROADMAP & PHASED DEVELOPMENT

1. Phase 1 (MVP Launch)

Private & Confidential www.zepul.com

 ●​ User onboarding, basic feed, two perspectives, editorial uploads, fundamental
analytics.
●​ Prioritize acquiring steady content streams via RSS or API partnerships.

2. Phase 2
●​ Integrate advanced features: push notifications, AI-based perspective tagging,
advanced admin dashboards, improved moderation.
●​ Introduce multi-language expansions (e.g., more Indian languages).

3. Phase 3
●​ Monetization strategies (ads, subscriptions), fully automated perspective classification,
online access.
●​ Potential expansions to web crawling (scraping) and more publisher partnerships.

4. Phase 4
●​ Deeper personalization with ML recommendations, advanced editorial workflows,
global language coverage.
●​ Potential pivot or expansions to user-generated news content (like citizen journalism).

RISKS & DEPENDENCIES

1. Legal & Compliance

●​ Must respect publisher copyrights, local news regulations, content usage rights.
●​ Scraping policies (robots.txt compliance).

2. Data Quality & Source Reliability

●​ Ensuring the aggregator doesn’t serve fake news or biased coverage inadvertently.
●​ Partnerships with credible sources, or disclaimers regarding unverified sources.

3. Scalability
●​ Trakic spikes during major breaking events; must ensure the system can scale.

4. User Adoption & Engagement

●​ Need strong marketing, user feedback loops for a broad user base.
●​ Must keep the user interface intuitive to retain less tech-savvy audiences.

5. Technical Overhead
●​ Multiple language support, perspective classification, content ingestion all require
robust infrastructure and dev hours.

SUCCESS & CRITERIA METRICS

1. User Adoption
●​ Number of sign-ups, daily active users (DAU), monthly active users (MAU).

2. Engagement
●​ Likes, comments, shares, average session duration, average articles read per
session.

3. Content Quality
●​ Editor rating, user feedback, content diversity (variety of categories and
sources).

4. Operational Metrics
●​ Time to ingest news from sources, frequency of errors in ingestion, dashboards load
times.

Private & Confidential www.zepul.com

5. Revenue (Long-Term)
●​ Ad impressions, subscription conversions, or any other monetization channels.

ESSENTIALS FOR MVP

1.User Onboarding & Profile

1. Phone/Email Registration (OTP-based)

●​ Low friction sign-up with automatic user validation.
●​ Saves minimal user profile data (name/phone/email).

2. Terms & Conditions Acceptance

●​ Clear disclaimers on usage, data privacy, and content sourcing.

Rationale: Quick, easy onboarding gets new users into the app rapidly, while T&Cs cover legal
essentials.

2. Core News Feed

1. Basic Aggregation of News Stories

●​ Pull articles from a few reliable feeds (RSS/API) to ensure a steady flow of content.
●​ Tag or categorize them (Politics, Finance, Sports, etc.).

2. Two Perspectives Display (Primary USP)

●​ Display brief “Left” vs. “Right” viewpoints side by side on the story page.
●​ Keep it simple at first: one main perspective and a button/toggle to reveal the second.

3. “Full Coverage” Button (Basic Version)

●​ Link to a list of related articles covering the same story/event.
●​ Start with a straightforward approach: link only to 2–3 relevant sources (either curated
manually or from your aggregator).

Rationale: Showcasing multiple perspectives is the core differentiator. Start with minimal
categories and curated perspectives to prove the concept without overcomplicating the data
ingestion.

3. User Engagement

1. Likes & Shares

●​ Let users quickly react and share stories externally (e.g., WhatsApp, social media).
●​ Shared link should show a teaser (one perspective); full story reveals both sides
in-app.

2. Comments (Basic)
●​ Enable simple text comments under each article to foster community discussion.
●​ Minimal moderation tools (e.g., hide inappropriate language) can come later.

3. Bookmarks / Saved Articles

●​ Users can save articles for reading later.
●​ Bookmarks accessible via a simple “My Bookmarks” screen.

Rationale: Likes, shares, and bookmarks are easy engagement wins. Comments can be
limited but included in an MVP if resources allow, as it enhances stickiness and user

Private & Confidential www.zepul.com

interaction.

4.Basic Admin & Editor Dashboards

1. Story Creation & Editing

●​ Allow internal editors to write or modify stories in at least one language (e.g., English).
●​ Optionally enable Telugu as a second language if it’s straightforward for your editorial
team.

2. Basic Analytics
●​ Simple view of top stories, daily/weekly/monthly visits, and user engagement
(likes/shares).
●​ Must-have stats for iterative improvements and content strategy.

3. Role-Based Access
●​ Editor: Can create/edit/publish stories.
●​ Admin: Same plus the ability to see analytics.
●​ Super Admin (if needed): Manage user roles and app-wide settings.

Rationale: At an MVP level, you need only a simple dashboard for internal users to upload
stories and track basic performance. Over time, you can add advanced approval flows and
deeper analytics.

5. Sentiment Meter (Simplified)

1. Display Basic Sentiment Indicator

●​ Could be as simple as showing how many likes each perspective is getting (Green vs.
Red).
●​ Keep it lightweight: no complex algorithm yet, just a tally of user reactions.

Rationale: This captures the “crowd’s preference” at a glance, reinforcing the dual
perspective concept.

6. Minimal Content Ingestion Setup

1. RSS/Atom Feed Integration

●​ Choose 2–3 high-quality news sources with open RSS feeds.
●​ Pull headlines and short summaries automatically.

2. Optional: Content Aggregation API

●​ If you can integrate a single aggregator (e.g., NewsAPI) for broader coverage without
heavy dev work.
●​ Keep monthly cost/usage in mind if it’s paid.

3. Manual/Editor Feed
●​ Allow editors to directly upload content or paste article summaries if feed
coverage is lacking.

Rationale: This balance ensures you have fresh, automated news plus manual curation to
highlight your USP.

7. Basic Architecture & Performance

1. Responsive Front End

Private & Confidential www.zepul.com

 ●​ A single web app or a basic mobile app (depending on your go-to-market strategy).
●​ Optimize for quick load times and easy navigation.

2. Simple Back End with Caching

●​ Cache popular articles to reduce load and ensure snappy performance. o Cron
jobs or scheduled tasks to refresh feeds (every 15–30 minutes).

Rationale: MVP performance is best kept simple: focus on stability and a smooth user
experience before scaling up.

8. Feature Prioritization Within the MVP

1. Must-Have
●​ User Onboarding
●​ Core Feed with Two Perspectives
●​ Basic Engagement (Likes, Bookmarks, Shares)
●​ Editor Dashboard (Write/Edit Stories, Minimal Stats)
●​ RSS Feed Integration

2. Nice-to-Have (If Capacity Allows)

●​ Simple Commenting
●​ Sentiment Meter
●​ “Full Coverage” Linking (Even if just a small list of related articles) or
Multi-language editorial input (Telugu/English)

Tip: If engineering resources are limited, consider deferring features like advanced “Full
Coverage” clustering or complex comment moderation to a post-MVP phase.

9. Why This MVP Is Enough

●​ Validates Core Value Prop: Shows the dual-perspective approach in a

functional news aggregator.
●​ Builds Initial User Base: Basic engagement features (like, share, bookmark)
will help you attract and retain early adopters.
●​ Supports Early Monetization/Partnership: Even minimal analytics and content
ingestion set the stage for partner or investor discussions.

RESOURCE ALLOCATION
1. Team Composition & Skill Sets

To develop and launch an MVP in one month (and a refined release in two), you’ll need a
compact but highly efficient team. Here are the typical roles:

1. Product Manager (1)

●​ Defines roadmap, features, and priorities.
●​ Coordinates between stakeholders, handles backlog grooming, ensures timely
deliverables.

2. UI/UX Designer (1)

●​ Designs user flows, wireframes, final high-fidelity prototypes.
●​ Works closely with devs to ensure seamless user experience.

Private & Confidential www.zepul.com

3. Front-End Developers (2)
●​ Specialize in React
●​ Handle responsive web design or mobile app React Native for the user-facing
portion.
●​ Integrate with back-end APIs.

4. Back-End Developer (1)

●​ Builds APIs, manages database schema, ensures data ingestion from
RSS/APIs, implements role-based access for admins/editors.
●​ Oversees server configuration, possibly some DevOps tasks.

5. QA Engineer (1)
●​ Plans testing strategy (functional, regression, smoke testing).
●​ Tests end-to-end features, ensures bug fixes, verifies performance.
●​ Could be part-time if the team is small, or the responsibility can be partially
shared among the developers for an MVP.

6. DevOps / Cloud Engineer (Optional or Part-Time)

●​ Sets up continuous integration/continuous deployment (CI/CD).
●​ Manages infrastructure on AWS/Azure/GCP, configures containerization or
basic server.
●​ Could be combined with the back-end developer if they have DevOps
experience.

Total Full-Time Personnel: ~6 (1 PM, 1 UX, 2 FE devs, 1 BE dev, 1 QA)

Optional: 1 DevOps (part-time or folded into back-end dev).

2. Infrastructure & Tooling

1. Version Control & CI/CD

●​ GitHub or GitLab for code repository.
●​ GitHub Actions / Jenkins / GitLab CI for continuous integration and
deployment.

2. Project Management
●​ Jira, Trello, or Asana to manage sprints, tasks, and epics.

3. Design & Prototyping

●​ Figma or Sketch for UX/UI designs.
●​ Zeplin (optional) for dev handok.

4. Hosting & Deployment

●​ AWS / Azure / GCP or a container service (e.g., AWS ECS, Kubernetes). o A
staging and production environment.

5. Data/Database
●​ PostgreSQL or MySQL for relational data.
●​ Redis or a caching layer if needed for performance.
●​ Potential NoSQL store (MongoDB) if data is unstructured, but likely not mandatory for MVP.

6. RSS/News Aggregation
●​ Cron job or scheduled serverless function to pull data from RSS feeds or APIs every 15–30
minutes.
●​ Basic feed parser library (e.g., Feedparser in Python or node-feedparser in Node.js).

Private & Confidential www.zepul.com

TIMELINES AND MILESTONES (2 MONTHS)

Below is a sample sprint plan for a 2-month timeline with a 4-week MVP target. Each “Week”
could correspond to a sprint if you adopt one-week sprints, or you might group two weeks into a
single sprint with more robust planning.

Month 1 (MVP Development)

Week 1

• Planning & Requirements

●​ Product Manager finalizes feature scope for MVP.
●​ UX Designer delivers low-fidelity wireframes for user flows (onboarding, main feed, story
detail, admin).
●​ Back-End Dev sets up a basic project skeleton (database, frameworks). o Front-End Devs set
up initial front-end architecture.

• Key Deliverables:

●​ Confirmed MVP backlog in Jira/Trello.

●​ Basic service structure (repos, environment, continuous integration setup). o Low-fidelity UX
prototypes.

Week 2

• Core MVP Functionality

●​ Front-End: Implement user onboarding (OTP flow, T&C acceptance). Start building the main
feed UI (list of articles, categories).
●​ Back-End: Implement user login/registration endpoints, set up RSS feed ingestion pipeline
(basic version).
●​ QA starts writing test cases for user onboarding and feed ingestion.

• Key Deliverables:
●​ Onboarding flow functioning end-to-end.
●​ Data ingestion from at least one news source working in a development environment.

Week 3

• User Engagement & Editorial Tools

●​ Front-End: Like, share, bookmark features; basic article detail page with two perspectives
displayed.
●​ Back-End: Endpoints for likes, bookmarks, comments (if included in MVP). Basic editorial
endpoint for creating/editing stories.
●​ Admin Dashboard: Basic stats page outline (views, top stories).
●​ QA begins manual testing of completed features, logs defects.
●​ UX Designer finalizes any leftover screens (admin stats, sentiment meter, etc.).

• Key Deliverables:
●​ Story detail page with “Left vs. Right” perspective.
●​ Minimal editorial interface (web form) to publish a story.
●​ Partial admin analytics view (stubbed or partial data).

Week 4

Private & Confidential www.zepul.com

• MVP Finalization & Bug-Fixing
●​ Integrate or refine the “Full Coverage” button if feasible (or keep it as a simplified “Related
Articles” link).
●​ Implement sentiment meter (show likes/votes for each perspective). o QA does thorough
testing (functional, regression, smoke).
●​ Fix critical bugs, performance issues, refine UI.

• Key Deliverables:
●​ MVP ready to demo or soft-launch.
●​ All high-priority bugs fixed.
●​ Admin/Editor workflows functioning for basic publishing.

End of Month 1: MVP is feature-complete and tested at a basic level.

Month 2 (Refinements, Launch & Polish)

Week 5 & 6

Refinements & Feature Hardening

●​ Gather feedback from internal testing or a small beta group.
●​ Address UX improvements, handle corner cases in content ingestion (multiple RSS feeds,
deeper categories).
●​ Improve stability and performance (caching frequently accessed news). o Add minimal
comment moderation (if needed) or advanced admin stats if capacity allows.

Week 7

Pre-Launch Preparations
●​ Conduct load testing and finalize production infrastructure.
●​ QA covers performance testing, device/browser compatibility.
●​ Final brand/design polish (icons, color themes, microcopy).
●​ Begin marketing or pre-launch announcements.

Week 8

Official Launch & Post-Launch

●​ Deploy to production environment, finalize domain or mobile store listing (if it’s an app).
●​ Monitor live user data, fix urgent issues.
●​ Product Manager and team gather initial usage metrics (daily active users, story reads,
engagement).

End of Month 2: Project is live, refined from MVP feedback, stable enough for real users and
continued growth.

Gantt Chart for Development

Tasks / Weeks W1 W2 W3 W4 W5 W6 W7 W8

Finalize MVP Scope &

Requirements ■■■

Set Up Repositories &

Dev Environment ■■■

Private & Confidential www.zepul.com

Architecture & Feed
Parsing Strategy ■■■

User Onboarding &

Authentication ■■■

Basic News Feed Display ■■■

Wireframe to High-Fidelity
Design ■■■

Engagement Features
(Likes/Share/Bookmark) ■■■

Two-Perspective Story
View & Admin Panel ■■■

Basic Analytics (Story

Views/Stats) ■■■

“Full Coverage” Button

(Simplified) ■■■

Sentiment Meter & UI

Polishing ■■■

QA & Bug Fixes for MVP ■■■

Beta Testing & User

Feedback ■■■

Content Ingestion
Enhancements ■■■

“Full Coverage”
Button(Simplified) ■■■

Sentiment Meter & UI

Polishing ■■■

QA & Bug Fixes for MVP ■■■

Beta Testing & User

Feedback ■■■

Content Ingestion
Enhancements ■■■

Performance & Stability

Upgrades ■■■

QA & Minor Feature

Polish ■■■

Load Testing & Branding ■■■

Marketing & Launch Prep ■■■

Production Deployment &
Official Launch ■■■
Post-Launch Monitoring &
Metrics ■■■

CONCLUSION

Zepul is prepared to plan and execute the project within the specified timeframes.Customer
must evaluate this document and grant approval to allocate the appropriate resources so that
the timelines and the overall budget may be determined more precisely for a final go ahead.

Private & Confidential www.zepul.com

For Zepul For The Service Provider

Signature Signature

Name - Reena Sumera Name -

Designation - Director , Program Management Designation -

Date - 30 - December - 2024 Date -

Place - Hyderabad, Telangana Place -

**** END OF THE DOCUMENT ***

Private & Confidential www.zepul.com