a supplier tracking platform for ISO 27001 teams
PROJECT OVERVIEW
What this app does
This platform helps an internal ISO 27001 project team track approximately 20–30 suppliers. Team members can create, browse, view, and update basic supplier records, including service and contact information. The initial scope is a supplier register for project tracking.
As a supplier manager, I want to create a supplier record so that the supplier can be tracked in the ISO 27001 project.
As a supplier manager, I want to browse and view supplier records so that I can review the suppliers being tracked.
As a supplier manager, I want to update a supplier record so that its tracked information stays current.
The following user counts are projected totals after one year of growth
50
supplier_managers
Internal staff who maintain and review supplier records for the ISO 27001 project.
COST BREAKDOWN
How your requirements become a plan and a price
Momen doesn't give a vague quote: it first sizes the project's actual demand for each capability and resource, then costs each item out. The numbers in the 'Project demand' column below — their scale assumptions and derivations — are detailed in Scale & sizing
Minimum viable plan
BASIC
Multiple supplier-management workflows and ongoing use require BASIC.
See the capability-by-capability assessment ▾
PROJECT DEMAND
ALLOWANCE PROVIDED (COMPOSITION)
AI points add-on
x 0
0 points
not purchased
(plan/kit 1.0M points)
No requirement
$ 0
Outbound data transfer add-on
x 0
0 B/mo
not purchased
(plan/kit 2.00 GB/mo)
No requirement
$ 0
Object storage
add-on
x 0
0 B
not purchased
(plan/kit 2.00 GB)
No requirement
$ 0
Database storage add-on
x 0
21.02 MB
not purchased
(plan/kit 200.00 MB)
Covered by plan/kit (margin ~851%)
$ 0
single-tenant kit
x 0
1 req/s
not purchased
(plan/kit 5 req/s)
Covered by plan/kit (margin ~400%)
$ 0
Basic
x 1
Basic is the minimum viable plan
Basic
(Plan tier: BASIC)
See minimum viable plan above
$ 39
plan + add-ons · usage-based · no development cost
WHY MOMEN
Your options for this project
In the table below, the 'monthly infrastructure' for the self-built / AI routes is derived from the AWS list prices shown below, sized against this project's actual usage. Figures cover infrastructure and operations only — AI usage is billed separately and excluded here, so they don't match the $39/mo all-in above.
Current usage sizing
AWS list pricing
0.00 GB (first 100GB free)
Internet egress → 0
0.00 GB-month
S3 Standard → 0
0.02 GB-month
RDS gp3 storage → 0
2 × db.m6g.large (Multi-AZ) × 730h
RDS PostgreSQL db.m6g.large → 232.14
2 × t4g.large × 730h
EC2 t4g.large → 98.11
Total ≈ $330.25 / mo
Pure cloud resources
DEVELOPMENT COST
MONTHLY CLOUD INFRA ($/MO)
MONTHLY TOTAL (INFRA + OPS, EXCL. AI USAGE)
Traditional outsourcing / build in-house
about $35,000 - $55,000
≈ $330
Based on the AWS estimate above
≈ $2,330
Infra $330 + ops ~$2,000
4-6 months
5 / 5
Vibe Coding
about $5,000 - $9,000
≈ $330
Based on the AWS estimate above
≈ $1,830
Infra $330 + ops ~$1,500
hours
5 / 5
AI full-stack generation
about $2,000 - $4,000
≈ $330
Based on the AWS estimate above
≈ $1,830
Infra $330 + ops ~$1,500
hours
3 / 5
Off-the-shelf SaaS / vertical solution
$0
N/A
Priced per seat, not by cloud infra
≈ $16,000+
Per-seat pricing, tens of thousands of users
days
1 / 5
Momen
Recommended
$0
$39
All-in: egress / storage / auto-scaling; excludes AI usage
$39
hours
5 / 5
Servers, databases, traffic and storage are inherent infrastructure costs for this project — you pay them whether you outsource, use Cursor or Lovable, or build it yourself (self-built runs ≈ $330.25/mo at AWS list prices, often more), on top of the dev and ops staff you'd need to hire. Momen bundles all of it into $0/mo all-in and removes the need for an ops team.
The frontend can be generated with AI tools (Cursor, Lovable, etc.); the hard part is the backend — auth, database, scaling, data security and ops. Momen delivers a production-grade backend as a BaaS: keep the vibe-coding speed on the frontend, while the backend runs on proven infrastructure — reliable, with no self-hosting or ops.
SCALE & SIZING
What scale this estimate assumes, and how the numbers are derived
Cost depends heavily on usage volume. First see the key assumptions and business scenarios this estimate uses, then the full calculation derived from each scenario for every resource — all adjustable to your real situation
We assume this is an internal supplier-tracking tool rather than a public product. The stated 20–30 suppliers are records being tracked, not registered users; with no internal headcount provided, the internal tool category anchor of 50 registered accounts is a conservative planning assumption that can be adjusted to match the actual team.
We assume supplier records and their basic details are added and maintained gradually because this is an internal project-tracking tool rather than a system launched with a full pre-existing dataset. The standard linear-growth assumption of 225 equivalent days is appropriate; a full initial import or a different rollout pattern would justify adjusting it.
Routine Supplier Register Work
Routine Supplier Register Work
30
times/month
0 req/s
Peak load
We assume supplier-register activity is spread across normal working hours rather than triggered by a synchronized external event. The broad workday is modeled as one routine scenario, with separate purposes for directory browsing, creating records, reviewing details, and saving updates so reads are not conflated with write outcomes. An eight-hour period is used as the representative daily window, occurring on each of the 30 days in a typical month; if the team works only on weekdays, the monthly frequency can be adjusted.
Main impact: Peak Concurrency
The scenarios above set the assumptions for each resource; below is the full calculation derived from them. Click to expand each item.
DEVELOPMENT SCOPE
How this app works
What exactly does this budget support? Broken down by business scenario, showing the pages, data tables, automation flows and AI assistant behind each one
An internal manager finds a supplier, reviews its details, and updates the record if needed.
Supplier Directory Page
suppliers
An internal manager reviews the supplier register and adds a supplier record when needed.
Supplier Directory Page
suppliers
page
data_table
Supplier Detail Page
A detail and editing screen for reviewing and maintaining an individual supplier record.
Supplier Directory Page
A directory for internal users to browse, filter, and add supplier records.
FAQ
What you might want to know about this project
The Q&A below is generated by AI based on this project's type, features and scale
What would most affect the platform's resource usage?
Does the initial scope include supplier assessments or evidence collection?
How does the estimated scale account for the 20–30 suppliers?
Copy to discuss with AI
Challenge & re-estimate
Master Momen with step-by-step guidance
Master Momen with step-by-step guidance
Engage and receive hands-on support
Engage and receive hands-on support
Watch and learn how apps are built in Momen
Watch and learn how apps are built in Momen
The latest news, cases, and resources
The latest news, cases, and resources
