Solo Developer Project Management: Notion + Feishu for One-Person Operations
How solo developers can build a complete project management system using Notion and Feishu. Product roadmap, client tracking, supplier management — zero cost, maximum efficiency.
Why Solo Developers Need Project Management
"I'm just one person. Isn't project management overkill?"
This is the most common response from solo developers. But the truth is the opposite: being solo makes project management more essential, not less.
Without a team, everything lives in your head: feature priorities, client requests, bug fixes, marketing plans, financial records. Research shows working memory can only hold 3–5 information chunks simultaneously. Beyond that, decision quality plummets.
The Cost of No System
- Feature creep: Today feature X seems urgent, tomorrow feature Y is critical. Three months later, your product is a Frankenstein.
- Client neglect: Promised client A delivery Wednesday, client B a demo Friday. You forgot both.
- Supplier chaos: API key expired. Domain renewal missed. Server bill overdue.
- Decision fatigue: Spending hours deciding "what to do next" instead of actually doing it.
This guide shows you how to build a zero-cost, lightweight, complete PM system using Notion + Feishu (Lark) + automation tools.
The Tool Stack
| Tool | Purpose | Cost |
|---|---|---|
| Notion | Product roadmap, feature backlog, tech docs | Free (personal plan) |
| Feishu (Lark) Base | Client management, supplier tracking, finances | Free |
| Make.com / n8n | Connect Notion and Feishu — automated workflows | Free tier (1,000 ops/mo) |
Part 1: Notion — Product Development Roadmap
1.1 Core Database Structure
Create these 4 databases in Notion:
Database 1: Feature Backlog
| Field | Type | Description |
|---|---|---|
| Feature Name | Title | Concise description |
| Status | Select | Backlog / Planned / In Dev / Live / Deprecated |
| Priority | Select | P0(Critical) / P1(High) / P2(Medium) / P3(Low) |
| Value Score | Number | 1–10 based on user & business value |
| Dev Effort | Number | Estimated person-days |
| User Source | Text | Which client or channel requested this |
| Linked Goal | Relation | Link to Product Goals database |
Database 2: Product Goals
| Field | Type | Description |
|---|---|---|
| Goal Name | Title | OKR or quarterly objective |
| Period | Date | Start and end dates |
| Key Results | Text | Success metrics |
| Progress | Percent | Auto-calculated from linked features |
Database 3: Sprint Board
A Kanban view grouped by status:
To Do → In Progress → In Review → Done
Each card includes: task description, deadline, assignee (you), linked feature.
Database 4: Tech Docs
| Field | Type | Description |
|---|---|---|
| Doc Title | Title | e.g., "API v2 Design" |
| Type | Select | Architecture / API / Deployment / Database |
| Linked Feature | Relation | Link to Feature Backlog |
| Last Updated | Date | Auto-recorded |
1.2 Database Relations
Link the databases using Notion's relation feature:
Product Goals ← Feature Backlog ← Sprint Board
↘ Tech Docs
This lets you drill from "Q3 Growth Goal" all the way down to "API docs for the feature you're building."
1.3 Views Configuration
Create different views of the same database:
- Timeline View (roadmap): On the Feature Backlog, sorted by priority — drag to reschedule
- Kanban View: For the Sprint Board — drag cards to change status
- Table View: For batch editing and export
- Calendar View: For milestones and delivery dates
Part 2: Feishu Multidimensional Tables — Client & Supplier Management
2.1 Client Management Table
| Field | Type | Description |
|---|---|---|
| Client Name | Text | Individual or company |
| Contact Info | Text | WeChat / Email / Phone |
| Client Type | Select | Paid / Lead / Partner |
| Service Status | Select | Consulting / Contracted / Active / Completed / Lost |
| Contract Value | Currency | Signed amount |
| Amount Received | Formula | Auto-calculated |
| Last Contact | Date | Last communication |
| Next Follow-up | Date | Reminder trigger |
| Notes | Text | Conversation summary |
Views:
- Default: All clients
- Follow-up Today: Filter "Next Follow-up" = today
- High Value: Filter contract value > $700
- Churn Risk: "Last Contact" > 30 days, status not "Lost"
2.2 Supplier Management Table
| Field | Type | Description |
|---|---|---|
| Supplier Name | Text | e.g., AWS / Stripe / DigitalOcean |
| Service Type | Select | Cloud / Payment / API / Design / Dev |
| Contract Expiry | Date | Renewal reminder |
| Monthly Cost | Currency | Estimated |
| Emergency Contact | Text | Support phone/email |
| Account Status | Select | Active / Expiring / Expired / Migrating |
| Notes | Text | Credential hints (never plaintext) |
Key Alerts:
- Yellow flag: 30 days before expiry
- Red flag: 7 days before expiry
- Budget warning: monthly cost exceeds threshold
Part 3: Automation — Connecting Notion and Feishu
This is the glue that makes the system sing.
3.1 Make.com Scenarios
Scenario 1: New Feature Alert
When you add a new feature request in Notion:
- Make.com watches for new rows in the Feature Backlog
- Auto-sends a message to your Feishu group: "New feature: [name], Priority P1"
- If P0, sends an urgent Feishu notification
Scenario 2: Client Follow-up Reminder
- Every day at 8 AM, Make.com scans the Feishu client table
- If "Next Follow-up" is today, sends a Feishu reminder message
- If not followed up for 3 consecutive days, escalates reminder frequency
Scenario 3: Supplier Renewal Alert
- Daily scan of supplier "Contract Expiry" field
- 30 days before: "[Service] expiring soon, prepare for renewal"
- 7 days before: Urgent notification + auto-create a Notion task
3.2 Manual Alternative (No Automation)
If you'd rather skip Make.com/n8n:
- Daily standup (with yourself): Open Notion board + Feishu client table every morning. 5-minute plan.
- Weekly review: Sunday, 30 minutes to update all databases.
- Phone reminders: Set daily Feishu reminders (e.g., 9 AM "Check today's tasks").
Part 4: Complete Workflow Example
You're a solo SaaS developer building an invoicing tool for small businesses.
Monday Morning
- Open Notion timeline: "Batch PDF export" feature (P1) is scheduled for this week
- Open Feishu client table: Client Zhang's "Next Follow-up" is today — he reported an Excel import bug last week
- Spend 30 minutes fixing the bug, message Zhang in Feishu
- Move bug fix to "Done" in Notion, start "Batch PDF Export" development
Mid-Week
- New client request auto-creates a Notion feature card via Make.com
- Feishu pops: "New P2 feature needs evaluation"
- Assess and schedule for next sprint
Sunday Review
- Notion Kanban: 4 tasks completed, 2 rolled over
- Feishu supplier table: Check domain renewal date
- Plan next week: 3 P1 features + 1 P0 bug fix
Part 5: Advanced Tips
5.1 Time Tracking Integration
Add a time tracking field in Notion (via Toggl or Clockify integration). Track actual hours per feature. Over months, you'll develop accurate effort estimates.
5.2 Financial Tracking
Add income/expense tracking in Feishu Base:
- Client payments auto-update "Amount Received"
- Supplier costs auto-summarize
- Monthly P&L auto-calculated
5.3 Template Reuse
Create a Notion + Feishu template for your next product:
- Notion: Database structure + views
- Feishu: Client table + supplier table + bot config
5.4 Weekly Auto-Report
Use Make.com to auto-generate a weekly summary:
- Features completed this week (from Notion)
- New clients and revenue (from Feishu)
- Send to your Feishu or email
Summary: The Solo Developer PM System
| Module | Tool | Setup Time | Core Value |
|---|---|---|---|
| Product Roadmap | Notion | 2 hours | Clear direction, no feature creep |
| Sprint Management | Notion Kanban | 1 hour | Daily focus, higher completion |
| Client Management | Feishu Base | 1 hour | Never miss a client |
| Supplier Management | Feishu Base | 30 min | No renewal surprises |
| Automation | Make.com | 2 hours | Tools talk to each other |
Total setup: One weekend (~6–7 hours) Monthly maintenance: ~1 hour Cost: $0
Quick Start Checklist
- Create Notion account (free)
- Create Feishu account (free)
- Build 4 Notion databases
- Set up Feishu client & supplier tables
- Configure 3 Make.com automation scenarios
- Define daily/weekly workflow SOP
Remember: This system isn't about adding management overhead. It's about freeing your brain from memory and decision tasks so you can focus on what matters — writing code and building great products.
Your tools should serve your workflow, not the other way around. If something feels off, change it. The solo developer's superpower is flexibility — you can tune the system until it perfectly matches your rhythm.
Great project management isn't about doing more. It's about doing the right things.