AIMultiple ResearchAIMultiple ResearchAIMultiple Research
We follow ethical norms & our process for objectivity.
This research is not funded by any sponsors.
AI
Updated on Apr 2, 2025

AGI Benchmark: Can AI Generate Economic Value in 2025

Headshot of Cem Dilmegani
MailLinkedinX

AI will have its greatest impact when AI systems start to create economic value autonomously.

We benchmarked whether frontier models can generate economic value. We prompted them to build a new digital application (e.g. website or mobile app) that can be monetized with a SaaS or advertising-based model. Benchmarked models:

Results

Both models provided comprehensive outputs to our prompts, decided the focus area of the website, and provided prompts for the Cursor AI code editor with instructions to build the website.

To be fair to both models, we relied on this prompt without making any further adjustments. The only exception was that when Cursor asked us whether to continue, we prompted it with phrases like “yes, continue please”.

Both websites could not be coded fully with Cursor. Although the code includes most of the core functionalities, Cursor failed to create a fully functioning website. So, we cannot continue with the further steps. They both completed 2% of our milestones.

Step 1: Choosing the focus of the website

We prompted the frontier models to choose a domain for their app:

Claude Sonnet 3.5’s response

Project management tool for freelancers:

Pricing Structure

  • Free Tier:
    • 2 active projects
    • 1 client
    • Basic invoicing
  • Pro Tier ($15/month):
    • Unlimited projects
    • Unlimited clients
    • Custom invoicing
    • Priority support
    • Advanced analytics

Our assessment

The competitors offer: One of the biggest competitors in the area, Clickup offers the same features for a cheaper price. Another top vendor in the area, Asana offers unlimited tasks, projects, messages, activity logs, and file storage (100MB per file) in its Free plan.

The output of the Claude Sonnet 3.5 failed to offer competitive pricing or a competitive feature to choose over the existing vendors in the field.

ChatGPT-o1

A specialized job board for businesses hiring AI-savvy content creators (writers, marketers, social media managers using AI tools, etc.)

Pricing structure:

  • Employer Plan: $199/month for unlimited postings OR $49 per job listing.
  • Job Seeker: Free to create a profile and browse.

Our assessment

This pricing model presents a straightforward, flat-fee structure that could be cost-effective for employers with frequent hiring needs, offering unlimited postings for a fixed monthly rate. However, for employers with infrequent postings or those preferring to pay fees proportional to transaction amounts, existing platforms like Upwork with minimal upfront costs and percentage-based fees might appear more economical.

Therefore, the suggestion of the ChatGPT-o1 may not appeal to either employers or employees.

Our research revealed that these models lack the ability to perform high-quality research since their output is not only a new idea, but also does not offer better features than its competitors. They still require human researchers to improve upon existing tools.

Also, Cursor (with Claude Sonnet 3.5 as the LLM used in coding for both projects) could not code an entire website. This failure could be attributed to either the Cursor’s limitations or inadequate prompting. Either way, without human participants, it was not possible to generate the idea and code the entire website in this benchmark.

You can also read our AI reasoning benchmark to see the model’s ability to reason.

Methodology

We selected the necessary milestones for AI systems to generate economic value by building new applications:

  • Domain identification (%1)
  • Spec preparation (%1)
  • App coding (%8)
  • App deployment (%5)
  • App testing (%5)
  • Marketing (%5)
  • Optimization (%5)
  • Revenue generation (%70)

Each milestone was assigned a specific budget and the results were evaluated by a human expert panel.

Tools could be used within the allocated budget for each model. We created accounts in various systems to test the models.

Our first prompt: Create a website with specific revenue targets. This process will include different phases for selecting the niche, coding and deploying, and marketing.

  • Business Goal: Generate $2,000 Monthly Recurring Revenue (MRR) within 2 months of deployment
  • Initial marketing budget: $500
  • Cannot implement any compliance and certification requirements (no HIPAA, SOC2, PCI, etc.) For Phase 1: Analyze and select one promising niche market that can:
  • Reach $2k MRR within 2 months realistically
  • Be built and marketed within our budget constraints
  • Have clear monetization potential
  • Show sufficient market demand
  • For Phase 2: I will code the product with an agentic AI coding editor, like Cursor, v0 etc.
    • You should provide me a prompt to give the editor. The prompt should include all the functions of the product. After that, we will continue with marketing, but for now, only provide results for these.

Since the models left some choices to the user, we prompted them again.

Our second prompt: Is there a specific AI coding assistant you want me to use? Cursor, Replit, V0, Lovable etc. Also, make sure that the prompt we give to these tools covers all the details of the project. Don’t make the AI coding assistant or me make a choice about the project, you will decide all the details about the project.

You can see the full outputs of the tools in the Outputs section.

Outputs

Outputs of the Claude Sonnet 3.5:

Answer to the first prompt:

I’ll help you analyze potential niches and create a development plan that fits your constraints. Let’s think through this systematically.

Phase 1: Niche Selection Analysis

Given your constraints:

  • Need for quick revenue ($2k MRR in 2 months)
  • Low initial marketing budget ($500)
  • No heavy compliance requirements
  • Need for clear monetization
  • Must have existing market demand

Recommended Niche: Freelance Project Management Tool Rationale:

  1. Market Validation:
  • Freelancing market continues to grow rapidly
  • Existing tools are often too complex or expensive for individual freelancers
  • Low compliance requirements since we’re not handling sensitive data
  1. Monetization Potential:
  • Target Price Point: $15/month for individual freelancers
  • To reach $2k MRR = ~134 paying customers needed
  • Realistic acquisition with $500 marketing budget through targeted ads and content marketing
  1. Clear Pain Points:
  • Project timeline tracking
  • Client communication management
  • Invoice and payment tracking
  • Simple file sharing
  • Basic task management

Phase 2: Development Prompt for AI Coding Assistant

Project Overview

Create a web-based freelance project management tool using Next.js and Typescript. The application should focus on simplicity and ease of use while providing essential features for freelancers to manage their projects, clients, and invoices.

Core Features

1. Authentication System

  • Email/password authentication
  • OAuth integration (Google)
  • User profile management
  • Subscription management integration

2. Project Management

  • Project creation and management
  • Project name, description, deadline
  • Project status tracking
  • Milestone creation and tracking
  • Time tracking functionality
  • Task management within projects
  • Task creation, assignment, and status updates
  • Due date management
  • Priority levels
  • Progress tracking

3. Client Management

  • Client profiles
  • Contact information
  • Project history
  • Communication history
  • Client portal for viewing project progress
  • File sharing capabilities

4. Invoice Management

  • Invoice generation
  • Payment tracking
  • Basic reporting
  • Integration with Stripe for payments

5. Dashboard

  • Overview of active projects
  • Upcoming deadlines
  • Recent activities
  • Time tracked this week/month
  • Outstanding payments

Technical Requirements

Frontend

  • Next.js with TypeScript
  • Tailwind CSS for styling
  • React Query for data fetching
  • Responsive design for mobile/desktop
  • Progressive Web App capabilities

Backend

  • Next.js API routes
  • PostgreSQL database
  • Prisma ORM
  • RESTful API architecture

Infrastructure

  • Vercel deployment
  • Supabase for database hosting
  • AWS S3 for file storage
  • Stripe integration for payments

Security Requirements

  • JWT authentication
  • Input validation
  • XSS protection
  • CSRF protection
  • Rate limiting
  • Secure file upload handling

Development Prompt for AI Coding Assistant

“Create a freelance project management web application using Next.js and TypeScript. The application should follow these key requirements:

  1. Initialize a Next.js project with TypeScript and set up the following:
  • Tailwind CSS for styling
  • Authentication using NextAuth.js
  • Prisma ORM with PostgreSQL
  • React Query for data fetching
  • Stripe integration for payments
  1. Implement the core features in this order:
  • User authentication and profile management
  • Project creation and management
  • Task management within projects
  • Client management and communication
  • Invoice generation and payment tracking
  • Dashboard with analytics
  1. Focus on creating a clean, intuitive UI that follows these principles:
  • Minimalist design
  • Clear navigation
  • Responsive layouts
  • Consistent styling
  • Accessibility compliance
  1. Implement proper error handling, loading states, and data validation throughout the application.
  2. Set up a CI/CD pipeline for automated testing and deployment to Vercel.

Please proceed step by step, starting with the project initialization and basic setup.”

MVP Timeline

Week 1-2: Core functionality

  • Authentication
  • Project management
  • Basic client management

Week 3-4: Additional features

  • Invoice management
  • Dashboard
  • File sharing
  • Stripe integration

Post-MVP Features

  • Time tracking
  • Expense tracking
  • Client portal
  • Advanced reporting
  • Template management
  • Integration with popular tools (Slack, Trello, etc.)

I’ve created a comprehensive development specification that focuses on a freelance project management tool. This niche was chosen because:

  1. Clear Market Need: Freelancers often struggle with juggling multiple projects and clients without expensive enterprise tools.
  2. Achievable Revenue Target:
  • Target 134 customers at $15/month within 2 months
  • Marketing can focus on freelance communities, forums, and targeted ads
  • Low customer acquisition cost through content marketing and word-of-mouth
  1. Technical Feasibility:
  • Can be built using modern web technologies
  • No complex compliance requirements
  • Scalable architecture
  • Clear MVP features for quick launch
  1. Marketing Strategy within Budget:
  • Focus on freelance platforms (Upwork, Fiverr)
  • Content marketing through Medium/dev.to
  • Targeted social media ads
  • Direct outreach to freelance communities

The development specification provides a detailed roadmap for building the MVP while keeping future scalability in mind. The AI coding assistant prompt is structured to guide development in logical phases while maintaining best practices.

Would you like me to elaborate on any particular aspect of the plan? We can also start discussing the marketing phase if you’re satisfied with the technical specification.

Answer to the second prompt:

For this project, I recommend using Cursor.ai as your AI coding assistant. It has strong capabilities with Next.js and TypeScript projects, and integrates well with VS Code. Let me provide a more detailed and prescriptive prompt that leaves no room for interpretation.

FreelanceFlow – Project Management Tool Development Specification

Project Overview

Create FreelanceFlow, a streamlined project management tool for freelancers using Next.js 14 with App Router and TypeScript. The application will use a monolithic architecture for quick development and early market entry.

Technical Stack (Specific Versions)

  • Next.js 14.0
  • TypeScript 5.0
  • TailwindCSS 3.3
  • Prisma 5.0
  • PostgreSQL 15
  • NextAuth.js 4.0
  • Stripe API v2023-10-16
  • React Query v5
  • Zod for validation
  • React Hook Form for form management
  • Vercel for hosting
  • Supabase for database hosting

Specific Design Decisions

  • Color Scheme:
  • Primary: #3B82F6 (blue-500)
  • Secondary: #10B981 (emerald-500)
  • Accent: #8B5CF6 (violet-500)
  • Background: #F9FAFB (gray-50)
  • Text: #1F2937 (gray-800)
  • Typography:
  • Inter font for body text
  • Font sizes: 14px body, 16px headings, 24px main headings
  • Layout:
  • Sidebar width: 280px
  • Maximum content width: 1200px
  • Responsive breakpoints: sm:640px, md:768px, lg:1024px, xl:1280px

Database Schema

model User {
  id            String    @id @default(cuid())
  email         String    @unique
  name          String?
  password      String
  projects      Project[]
  clients       Client[]
  invoices      Invoice[]
  createdAt     DateTime  @default(now())
  updatedAt     DateTime  @updatedAt
  subscription  Subscription?
}

model Project {
  id          String    @id @default(cuid())
  name        String
  description String?
  startDate   DateTime
  endDate     DateTime?
  status      ProjectStatus
  budget      Float
  userId      String
  clientId    String
  tasks       Task[]
  files       File[]
  user        User      @relation(fields: [userId], references: [id])
  client      Client    @relation(fields: [clientId], references: [id])
  createdAt   DateTime  @default(now())
  updatedAt   DateTime  @updatedAt
}

model Client {
  id          String    @id @default(cuid())
  name        String
  email       String
  phone       String?
  company     String?
  projects    Project[]
  userId      String
  user        User      @relation(fields: [userId], references: [id])
  createdAt   DateTime  @default(now())
  updatedAt   DateTime  @updatedAt
}

model Task {
  id          String    @id @default(cuid())
  title       String
  description String?
  dueDate     DateTime?
  status      TaskStatus
  priority    Priority
  projectId   String
  project     Project   @relation(fields: [projectId], references: [id])
  createdAt   DateTime  @default(now())
  updatedAt   DateTime  @updatedAt
}

model Invoice {
  id          String    @id @default(cuid())
  number      String    @unique
  amount      Float
  status      InvoiceStatus
  dueDate     DateTime
  userId      String
  user        User      @relation(fields: [userId], references: [id])
  createdAt   DateTime  @default(now())
  updatedAt   DateTime  @updatedAt
}

model File {
  id          String    @id @default(cuid())
  name        String
  url         String
  size        Int
  type        String
  projectId   String
  project     Project   @relation(fields: [projectId], references: [id])
  createdAt   DateTime  @default(now())
}

model Subscription {
  id          String    @id @default(cuid())
  stripeId    String    @unique
  status      SubStatus
  userId      String    @unique
  user        User      @relation(fields: [userId], references: [id])
  createdAt   DateTime  @default(now())
  updatedAt   DateTime  @updatedAt
}

enum ProjectStatus {
  PLANNING
  IN_PROGRESS
  ON_HOLD
  COMPLETED
  CANCELLED
}

enum TaskStatus {
  TODO
  IN_PROGRESS
  REVIEW
  COMPLETED
}

enum Priority {
  LOW
  MEDIUM
  HIGH
  URGENT
}

enum InvoiceStatus {
  DRAFT
  SENT
  PAID
  OVERDUE
  CANCELLED
}

enum SubStatus {
  ACTIVE
  PAST_DUE
  CANCELED
  UNPAID
}

API Endpoints

// Authentication
POST /api/auth/register
POST /api/auth/login
POST /api/auth/logout
GET /api/auth/session

// Projects
GET /api/projects
POST /api/projects
GET /api/projects/:id
PUT /api/projects/:id
DELETE /api/projects/:id

// Tasks
GET /api/projects/:projectId/tasks
POST /api/projects/:projectId/tasks
PUT /api/projects/:projectId/tasks/:taskId
DELETE /api/projects/:projectId/tasks/:taskId

// Clients
GET /api/clients
POST /api/clients
GET /api/clients/:id
PUT /api/clients/:id
DELETE /api/clients/:id

// Invoices
GET /api/invoices
POST /api/invoices
GET /api/invoices/:id
PUT /api/invoices/:id
DELETE /api/invoices/:id

// Files
POST /api/files/upload
DELETE /api/files/:id

// Subscription
POST /api/subscription/create
PUT /api/subscription/update
DELETE /api/subscription/cancel

Feature Implementation Details

1. Authentication Flow

  • Email/password registration with email verification
  • Google OAuth integration
  • JWT tokens with 24-hour expiration
  • Refresh token rotation
  • Password reset flow with email

2. Project Management

  • Kanban board view for tasks
  • List view for projects
  • Calendar view for deadlines
  • File attachment limit: 10MB per file
  • Maximum 50 active projects per user

3. Client Management

  • Client portal with unique login
  • Automated email notifications
  • File sharing with expiring links
  • Communication history logging

4. Invoice System

  • Automated invoice numbering (FORMAT: FF-YYYY-XXXXX)
  • PDF generation with custom templates
  • Stripe payment integration
  • Automatic payment reminders
  • Late payment tracking

5. Dashboard Analytics

  • Project completion rate
  • Revenue tracking
  • Time tracking
  • Outstanding payments
  • Upcoming deadlines

Pricing Structure

  • Free Tier:
  • 2 active projects
  • 1 client
  • Basic invoicing
  • Pro Tier ($15/month):
  • Unlimited projects
  • Unlimited clients
  • Custom invoicing
  • Priority support
  • Advanced analytics

Development Command Sequence

# 1. Project initialization
npx create-next-app@latest freelanceflow --typescript --tailwind --app

# 2. Install dependencies
npm install @prisma/client @next-auth/prisma-adapter @tanstack/react-query zod react-hook-form @stripe/stripe-js @uploadthing/react

# 3. Install dev dependencies
npm install -D prisma @types/node @types/react @types/react-dom eslint eslint-config-next

# 4. Initialize Prisma
npx prisma init

# 5. Set up database schema
# Copy the schema provided above to prisma/schema.prisma

# 6. Generate Prisma client
npx prisma generate

# 7. Run initial migration
npx prisma migrate dev --name init

Deployment Instructions

  1. Create Vercel account and install Vercel CLI
  2. Set up PostgreSQL database on Supabase
  3. Configure environment variables
  4. Deploy using Vercel CLI
  5. Set up CI/CD with GitHub Actions

Implementation Order

  1. Project setup and configuration
  2. Authentication system
  3. Database models and migrations
  4. API route implementation
  5. Core UI components
  6. Project management features
  7. Client management system
  8. Invoice generation and management
  9. File upload and management
  10. Subscription and payment integration
  11. Dashboard and analytics
  12. Testing and optimization
  13. Deployment and monitoring setup

Please proceed with creating each component exactly as specified. Start with the project initialization and base setup. Let me know when you’re ready for the next step or if you need any clarification.

I’ve created a comprehensive prompt that specifies every aspect of the project, leaving no decisions to interpretation. This prompt is specifically optimized for Cursor.ai and includes:

  1. Exact technical stack with specific versions
  2. Complete database schema
  3. All API endpoints
  4. Precise design specifications including colors and typography
  5. Detailed feature implementations
  6. Step-by-step development sequence

When using Cursor.ai:

  1. Create a new project directory
  2. Open it with VS Code + Cursor
  3. Copy this entire prompt into your first interaction
  4. Ask Cursor to proceed with the implementation in the specified order

The prompt is designed to be prescriptive enough that neither you nor the AI assistant will need to make additional architectural or design decisions. Each component, from the database schema to the UI components, has been explicitly defined.

Would you like to proceed with any particular section of the implementation, or would you like me to clarify any part of the specification?

Outputs of the ChatGPT-o1:

Answer to the first prompt:

Below is a two-part answer that addresses:

  1. Phase 1: Selecting one promising niche
  2. Phase 2: Providing a prompt for the agentic AI coding editor

Phase 1: Niche Selection

Recommended Niche:

A specialized job board for businesses hiring AI-savvy content creators (writers, marketers, social media managers who use AI tools, etc.).

Why this niche?

  1. Fast Route to $2k MRR
    • A job board can monetize quickly by charging employers for job listings or monthly subscriptions. With just 10–20 paying clients at $100–$200/month, you can reach $2,000 MRR.
  2. Budget-Friendly to Build & Market
    • Basic job board functionality (postings, profile creation, search, subscription billing) can be coded swiftly with standard web frameworks and integrated payment solutions. You can avoid deep compliance overhead (HIPAA, PCI, etc.) by relying on third-party processors like Stripe (Stripe handles the heavy-lift of compliance).
    • You can target marketing within a $500 budget by using LinkedIn outreach, niche Facebook/Reddit groups, and specialized communities such as AI writing forums.
  3. Clear Monetization Potential
    • Primary Revenue: Employer subscription fees (e.g., $199/month) for unlimited postings or per-job fees (e.g., $49/job).
    • Secondary Revenue (future): Sponsored listings or “featured job” upgrades.
  4. Sufficient Demand
    • AI-enabled content creation is booming; businesses across industries need copywriters and marketers who can leverage AI (ChatGPT, Jasper, MidJourney for visuals, etc.). Specialized job boards thrive if they quickly surface high-quality talent in a hot niche.

Sample Revenue Model

  • Employer Plan: $199/month for unlimited postings OR $49 per job listing.
  • Job Seeker: Free to create a profile and browse.
  • Goal: Acquire ~10 paying employers @ $199/month = $1,990 MRR (close to your $2k target).

Phase 2: Prompt for Agentic AI Coding Editor

Below is a structured prompt you can copy and paste into an agentic AI coding editor like Cursor or similar tools. It describes the overall product functionality and requirements. Feel free to adjust details (text, naming, etc.) to match your specific style or tech stack.

BEGIN PROMPT
Project Description:
Build a specialized job board called AI Content Jobs that connects businesses with AI-savvy content creators. The platform will provide job posting, user account management, and subscription billing.

Tech Stack/Requirements:

  1. Framework: Use a modern framework (e.g., Next.js, Django, Ruby on Rails) for rapid development.
  2. Database: Use a relational database (e.g., PostgreSQL) or a NoSQL option if preferred.
  3. Authentication: Implement secure user sign-up and login (JWT or session-based).
  4. Subscription Payments: Integrate with Stripe for processing payments.
  5. Compliance: Keep credit card data handling minimal by using Stripe’s secure checkout forms (avoiding our own PCI overhead).

Core Features:

  1. User Roles:
    • Employer: Can create/edit/delete job postings, subscribe to monthly plan, view applicants.
    • Job Seeker: Can create/edit profile, search & apply for jobs, manage applied jobs.
    • Admin: Manage site content, job postings, user accounts, subscription statuses.
  2. Employer Dashboard:
    • Create Job Post: Title, description, required skills, salary range, location/remote.
    • Manage Subscriptions: View current plan, billing cycles, cancel or upgrade subscription.
    • Manage Applicants: See who applied; contact them directly via email.
  3. Job Seeker Dashboard:
    • Create Profile: Name, contact info, AI tools expertise (ChatGPT, Jasper, MidJourney, etc.), portfolio links, resume upload.
    • Search Jobs: Filter by job title, location/remote, salary range, or key skill (e.g., AI copywriting).
    • Apply to Jobs: One-click apply or a simple short note to the employer with attached resume.
  4. Admin Panel:
    • Manage Job Postings: Approve or reject job listings if they violate policies.
    • Manage Users: Activate or deactivate accounts, change user roles.
    • View Payment History: Summaries of subscription fees, revenue, track MRR.
  5. Payment & Subscription Workflow:
    • Payment Plans:
      • Monthly Employer Plan: $199/month for unlimited postings OR pay-per-job at $49/post.
    • Stripe Integration:
      • Integrate Stripe checkout for all employer payments.
      • Webhooks for subscription status updates (activate, cancel, renewal, etc.).
  6. Notifications & Alerts:
    • Email Notifications:
      • To Employers when new applicants apply.
      • To Job Seekers when an employer views or responds to their application.
    • In-App Notifications (optional, if time): On dashboard for new applicants or new jobs.
  7. UI/UX:
    • Landing Page explaining the benefits of hiring AI-savvy writers/marketers.
    • Login/Register Page for Employers and Job Seekers.
    • Pricing Page for employers.
    • Job Listing Page with filters and search bar.
    • Profile/Resume Upload for job seekers.

Implementation Guidelines:

  1. Keep It Lean: Emphasize essential job board functionality first, then refine UI.
  2. Responsive Design: The site should be usable on desktop & mobile.
  3. Security: Store passwords hashed, use HTTPS for production.

Goal: Produce clean, well-documented code that can be deployed with minimal fuss to a service like Vercel, Heroku, or AWS. Provide a README detailing the setup steps, environment variables, and Stripe keys configuration.
END PROMPT

Next Steps (After Coding)

  1. Test & Launch: Conduct a soft launch among AI-writing communities. Gather early feedback.
  2. Marketing (High-Level Preview):
    • Use LinkedIn to connect with marketing directors or heads of content who need AI-driven copy.
    • Post in AI/Tech writing communities on Reddit, Facebook groups, Slack channels.
    • Offer limited-time discounts (e.g., 20% off first month).
    • Share success stories from early adopters once you have them.

With this approach and prompt, you’ll have a clear path to reach a niche audience, build your MVP quickly, and strive for $2,000 MRR within 2 months.

Answer to the second prompt:

Below is a comprehensive answer addressing your follow-up questions and providing a complete prompt you can copy/paste into an AI coding assistant of your choice (e.g., Cursor). This prompt includes all project details—so neither you nor the assistant has to make additional decisions. It also assumes the deployment target is Heroku.

Recommended AI Coding Assistant

I recommend using Cursor. It has a streamlined UI and powerful code-generation capabilities. However, you may also use V0, Replit, Lovable, or any agentic AI coding editor that supports multi-file output and dependencies. For consistency, the instructions below reference Cursor.

Single Prompt (Copy/Paste into the AI Coding Assistant)

BEGIN PROMPT

You are an expert AI coding assistant. Please create and configure a complete web application called AI Content Jobs, a specialized job board for employers to find AI-savvy content creators (writers, marketers, social media managers, etc.). The application should be built with the following strict requirements and no additional choices:

1. Tech Stack

  • Backend: Node.js (v16 or later) + Express.js
  • Frontend: React (Create React App or a similar setup)
  • Database: PostgreSQL
  • Payments: Stripe Integration for subscription and job listing fees
  • Deployment: Heroku

2. Folder / File Structure

Please create a single repository with the following structure (you can generate the files accordingly):

ai-content-jobs
├── backend
│   ├── package.json
│   ├── server.js
│   ├── config
│   │   └── db.js          // PostgreSQL connection
│   ├── controllers
│   │   ├── authController.js
│   │   ├── jobController.js
│   │   ├── subscriptionController.js
│   │   └── userController.js
│   ├── middlewares
│   │   └── authMiddleware.js
│   ├── models
│   │   ├── User.js
│   │   ├── Job.js
│   │   ├── Application.js
│   │   └── Subscription.js
│   ├── routes
│   │   ├── authRoutes.js
│   │   ├── jobRoutes.js
│   │   ├── subscriptionRoutes.js
│   │   └── userRoutes.js
│   ├── utils
│   │   └── emailService.js   // For sending notifications
│   └── .env.example
├── frontend
│   ├── package.json
│   ├── public
│   └── src
│       ├── App.js
│       ├── index.js
│       ├── components
│       ├── pages
│       └── services
├── .gitignore
├── Procfile        // For Heroku
└── README.md

Note: Feel free to split or combine files for clarity, but ensure the essential structure remains.

3. Detailed Requirements

3.1. User Roles

  1. Employer
    • Can create an account, log in, create/edit/delete job postings.
    • Can subscribe to a monthly plan for unlimited postings at $199/month, or pay $49 per job listing (one-time).
    • Can view all applicants for a job posting and contact them (email-based).
  2. Job Seeker
    • Can create an account, log in, create/edit a profile (skills, portfolio links, resume upload).
    • Can browse job listings, apply, track applications.
  3. Admin
    • Can view all job postings, edit or remove any if violating policies.
    • Can view all user accounts, manage them (activate/deactivate).
    • Can see subscription/payment details and overall site metrics (e.g., monthly revenue).

3.2. Authentication & Security

  • Use JWT-based authentication for secure login.
  • Store passwords with a strong hashing algorithm (e.g., bcrypt).
  • Protect employer/job seeker routes with middleware that checks user roles.
  • Basic rate limiting if possible (optional).

3.3. Job Posting & Application Flow

  1. Create a Job Post (Employer)
    • Title, description, required skills, location (remote or on-site), salary range, application instructions.
  2. Search & Filter (Job Seeker)
    • Filter jobs by skill, location, job type, etc.
  3. Apply (Job Seeker)
    • Submit a short note + attach resume from the user’s profile.
  4. Applicant Management (Employer)
    • View list of applicants per job post with contact info.

3.4. Stripe Payment Integration

  • Two Payment Options for Employers:
    1. Monthly Subscription Plan at $199/month (unlimited postings).
    2. Pay-Per-Job at $49 per listing.
  • Use Stripe’s secure checkout forms or Stripe Checkout for minimal PCI overhead.
  • Store subscription statuses in the Subscription model (start date, end date, cancellation date, plan type).
  • Webhooks or Stripe events to update subscription status.

3.5. Notifications

  • Email
    • An employer should receive an email when a new application arrives.
    • A job seeker should receive an email when an employer reviews/accepts their application.
  • Use a simple Node mailer library or 3rd-party service like SendGrid. For this prompt, a dummy function or console.log is okay if full integration is too time-consuming.

3.6. Frontend Requirements

  • Landing Page: Highlights the benefits of hiring AI-savvy content creators; includes calls to action.
  • Employer Dashboard (once logged in):
    • Manage job posts (create/edit/delete).
    • View subscription status, link to manage billing.
    • View applicants for each job post.
  • Job Seeker Dashboard:
    • Update personal info, AI tools proficiency, resume link/file, portfolio links.
    • Browse and apply to jobs; track applications.
  • Login/Register pages for both roles (can be one unified page or separate).
  • Pricing page that explains $199/month vs $49 per listing.

3.7. Database Schema (High-Level)

  1. users
    • id (PK)
    • email, passwordHash, role (employer, jobseeker, admin)
    • name, location, skills, portfolioLinks, resumeURL, etc.
    • createdAt, updatedAt
  2. jobs
    • id (PK)
    • employerId (FK -> users.id)
    • title, description, skillsRequired, location, salaryRange, etc.
    • isActive (boolean), createdAt, updatedAt
  3. applications
    • id (PK)
    • jobId (FK -> jobs.id)
    • jobSeekerId (FK -> users.id)
    • coverNote (text)
    • status (applied, viewed, shortListed, rejected, etc.)
    • createdAt, updatedAt
  4. subscriptions
    • id (PK)
    • employerId (FK -> users.id)
    • planType (“monthly” or “perJob”)
    • stripeSubscriptionId (for monthly) or stripePaymentId (for single payment)
    • startDate, endDate, isActive, createdAt, updatedAt

4. Heroku Deployment Instructions

  1. Root Files
    • Include a Procfile at the repo root with something like:
web: node backend/server.js

Make sure your backend package.json has a start script: "start": "node server.js".

2. Environment Variables

  • DATABASE_URL for PostgreSQL (Heroku Postgres add-on).
  • STRIPE_SECRET_KEY for server-side Stripe calls.
  • STRIPE_PUBLISHABLE_KEY for client-side.
  • JWT_SECRET for authentication.
  • Possibly SENDGRID_API_KEY or similar if using a 3rd-party email service.

3. Build & Deploy

  • Inside backend, run npm install.
  • Inside frontend, run npm install + npm run build.
  • Serve the React build output either statically from backend or as a separate app.
  • Push the repo to a new Heroku app.
  • Provision Postgres (e.g., heroku addons:create heroku-postgresql:hobby-dev).
  • Run DB migrations/seeds if needed.

5. Project Delivery

  • Generate the code for all components (backend + frontend).
  • Provide a README.md with step-by-step instructions for:
    1. Cloning the repo.
    2. Setting up .env variables locally.
    3. Installing dependencies.
    4. Running the development servers for both backend & frontend.
    5. Deploying to Heroku (including environment variables setup).
  • Ensure no additional prompts are required; embed all decisions here.

Goal: Produce a fully functional MVP codebase in a single pass, with no ambiguous “ask user to decide” logic.

END PROMPT

Explanation of the Prompt

  • One Prompt, All Decisions: The prompt fully specifies the tech stack (Node/Express/React/Postgres), the database schema, route structure, user roles, authentication, payment logic, and Heroku deployment.
  • No Compliance: We explicitly avoid PCI/HIPAA/SOC2, etc. by delegating payments to Stripe Checkout.
  • Heroku: The prompt instructs the AI to create a Procfile and to detail environment variables for the Heroku environment.

You can simply copy/paste the BEGIN PROMPT … END PROMPT text above into Cursor (or your preferred assistant), and it should generate a self-contained project with the specified details.

Final Notes

  1. Recommended Use: After the AI generates the code, review and polish any UI/UX details, test Stripe’s checkout flow with test keys, and confirm email notifications work as expected.
  2. Marketing & Budget: Once deployed, you’ll have $500 for your marketing push—focusing on targeted LinkedIn outreach, posts in AI-focused communities, and small-scale paid ads, if desired.

This concludes the instructions and the full prompt. Enjoy building AI Content Jobs and good luck reaching your $2k MRR goal!

FAQ

What is artificial general intelligence (AGI)?

Artificial General Intelligence (AGI) is a concept in computing research that describes an AI system that is at least as capable as a human at most tasks.
AGI is a system that can efficiently acquire new skills outside of its training data.
Intelligence lies in broad or general-purpose abilities, marked by skill acquisition and generalization, rather than the skill itself.
Such models can perform tasks that require human intelligence, like high-quality research, economically valuable work, and engineering tasks.
This benchmark is different from the present benchmarks, such as the ARC-AGI benchmark, since we aim to measure real-world challenges more directly. ARC AGI test includes an input grid and an output grid and wants AI models to detect the pattern in the input grid, and by following that, solve the output puzzle.1

How do human intelligence and AI models interact?

AGI capabilities alone do not determine destiny about risk but must be considered in combination with contextual details.
The affordances of user interfaces for AGI systems have a substantial bearing on risk profiles.
Carefully considered choices around human-AI interaction are vital to the safe and responsible deployment of frontier AI models.
Artificial General Intelligence (AGI) is a concept with both aspirational and practical consequences.
The development of AGI benchmarks and frameworks is crucial for assessing risks and progress in AI research.
Further research is needed to understand the potential risks and benefits of AGI and to develop safe and responsible artificial intelligence systems.
As researchers risk developing models capable of increasingly general intelligence, it becomes crucial to establish robust safety protocols and ethical guidelines before potential AGI systems emerge.
Technical evaluations showed the AI model achieved varying results across different research tasks, with frontier models significantly faster than previous iterations. The system’s ability to iterate on its own training code has sparked discussions about concrete steps toward AGI, though significant challenges remain in ensuring safety and robustness.

Share This Article
MailLinkedinX
Cem has been the principal analyst at AIMultiple since 2017. AIMultiple informs hundreds of thousands of businesses (as per similarWeb) including 55% of Fortune 500 every month.

Cem's work has been cited by leading global publications including Business Insider, Forbes, Washington Post, global firms like Deloitte, HPE and NGOs like World Economic Forum and supranational organizations like European Commission. You can see more reputable companies and resources that referenced AIMultiple.

Throughout his career, Cem served as a tech consultant, tech buyer and tech entrepreneur. He advised enterprises on their technology decisions at McKinsey & Company and Altman Solon for more than a decade. He also published a McKinsey report on digitalization.

He led technology strategy and procurement of a telco while reporting to the CEO. He has also led commercial growth of deep tech company Hypatos that reached a 7 digit annual recurring revenue and a 9 digit valuation from 0 within 2 years. Cem's work in Hypatos was covered by leading technology publications like TechCrunch and Business Insider.

Cem regularly speaks at international technology conferences. He graduated from Bogazici University as a computer engineer and holds an MBA from Columbia Business School.
Şevval is an AIMultiple industry analyst specializing in AI coding tools, AI agents and quantum technologies.

Next to Read

Comments

Your email address will not be published. All fields are required.

0 Comments