Before we dive into today’s 5 new ideas, we have something big to share.
Over the last 18 issues, we’ve published 100 project ideas — all designed to help software engineers start building.
But here’s the thing…
Many of you told us you still haven’t found your idea yet.
So, we decided to fix that.
✨ Introducing No Idea → noidea.one
It’s a growing library of real-world, ready-to-build project ideas — each small enough for a weekend, but big enough to become something real.
If you’ve been waiting for the right idea to start your next side project…
this is where you’ll find it.
Join the waitlist to access our exclusive pre-launch deal!
Intro
This weekend: Tools for the maker economy
All five ideas this week solve the same meta-problem: the hidden operational tax of running a small-scale physical production business.
Whether you’re running a 3D printing service, shipping hardware prototypes, or managing a makerspace, you’re bleeding time and margin on decisions that feel manual because the software world hasn’t caught up to your scale.
We found these pain points in r/3Dprintmyfile, Etsy seller forums, and makerspace Slack channels, places where people are making things work but constantly asking, “Isn’t there a better way?”
Pick one, build it in a weekend, and you’ll have users who’ve been waiting for someone to care about their niche.
Want a quick snapshot of this week’s top ideas? Grab our one-page teaser and get all 5 concepts at a glance
Table of Contents
1. PrintQueue Sync
Drop files in one folder, they route to the right printer automatically
Target Customer
Educators managing 3-8 different 3D printer brands in a lab or makerspace who waste time manually selecting printers for each job
The Problem
Desirable Outcome
Spend zero mental energy deciding which printer gets which file—the system routes based on simple rules you set once
Problem Description
Manual print job routing chaos
You waste 5-10 minutes per print job deciding which printer is free and compatible
Students submit files with no printer specified, creating a coordination nightmare
No single view of which printers are idle vs. busy across different brands
Each printer brand requires opening its specific software to queue a job
Business Opportunity
PrintQueue Sync
Watch a single folder (Dropbox/Google Drive) and auto-route .stl/.gcode files to the right printer based on filename tags or file size rules
Idea Breakdown
Project Type
Service
Core Feature
File watcher service that reads simple routing rules (e.g., ‘files tagged #prusa → Prusa printer’, ‘files >50MB → Creality’) and forwards to printer APIs
Main User Scenario
Educator sets up one shared Dropbox folder that students can access
Educator configures 3 simple rules in a config file (e.g., filename contains ‘prusa’ → Prusa MK3, file >100MB → Creality CR-10, default → Ender 3)
Student drops ‘prototype_prusa.stl’ into the folder
Service detects file, matches ‘prusa’ tag, sends to Prusa’s API (OctoPrint/PrusaConnect)
Student gets notification: ‘Queued to Prusa MK3 (position 2 in queue)’
Quick Start Steps
Core Routing Engine
tools: Node.js + chokidar (file watcher), Pocketbase (self-hosted on Fly.io - stores printer configs + routing rules), SQLite (via Pocketbase for zero-cost persistence), OctoPrint REST API (most common 3D printer interface)
skills: File system monitoring, REST API calls, Basic pattern matching
key decisions/validations: Service watches a local folder, matches files against rules stored in Pocketbase, forwards to OctoPrint instances. Using Pocketbase vs. Firebase saves $25/mo + eliminates OAuth complexity (just API keys); Drop a test file with ‘prusa’ in filename → it appears in the correct printer’s OctoPrint queue within 10 seconds
Cloud Folder Integration
tools: Dropbox API (free tier: 2GB), Webhook listener (Fly.io free tier), Node.js file sync
skills: OAuth 2.0 basics, Webhook handling
key decisions/validations: Watch shared Dropbox folder instead of local folder so multiple users can drop files remotely; Student uploads file to Dropbox → service routes it within 30 seconds → student sees confirmation
Simple Admin UI
tools: Bolt.new (rapid UI generation), React + Vite, Tailwind CSS, Pocketbase JS SDK
skills: CRUD forms, API integration
key decisions/validations: Web page where educator adds printers (name, OctoPrint URL, API key) and routing rules (if filename contains X → printer Y); Educator adds new printer and rule in <2 minutes without touching config files; printers_configured >= 3; successful_auto_routes >= 10
Deploy & Validate
tools: Fly.io (Node.js service + Pocketbase - free tier sufficient), Vercel (admin UI), Dropbox webhook endpoint
skills: Process management, Environment variables
key decisions/validations: Service runs 24/7, watching cloud folder, routing to multiple printers; 5 educators each route 10+ print jobs over a week without manual printer selection; active_educators >= 5; total_routed_jobs >= 50
3 Reasons to Consider This Idea
Solves the switching cost problem without rebuilding printer software — Works with existing OctoPrint/PrusaConnect setups—no need to replace what’s working, just adds the missing routing layer
Students don’t need training on multiple printer UIs — They just drop files in Dropbox with a naming convention—the system handles the rest
Natural expansion to load balancing — Once routing works, next step is ‘send to least busy compatible printer’ instead of fixed rules
Is This Idea For You?
✅ Comfortable with file system APIs and webhooks
✅ Can work with REST APIs (OctoPrint is well-documented)
✅ Interested in infrastructure/automation tools rather than visual interfaces
✅ Have access to 2+ 3D printers for testing (or willing to mock the APIs)
Closing Considerations
This isn’t a printer control panel—it’s the missing ‘traffic cop’ that sits in front of existing panels like OctoPrint and PrusaConnect. Existing solutions (OctoPrint, Repetier Server) manage individual printers well but don’t handle multi-brand routing from a single drop point. Start with just OctoPrint support (covers 60%+ of hobbyist/edu printers), add PrusaConnect/Bambu API later. The Dropbox integration is key—it makes this accessible to students without VPN or direct network access to printers.
Core Promise: You’ll route print jobs to the right printer in 3 seconds instead of 5 minutes, with zero clicks after initial setup
2. Print Time Pricer
Instantly price custom 3D print jobs based on actual machine time and material used
Target Customer
3D printing service providers who do custom orders and struggle to quote prices that cover their time and costs
The Problem
Desirable Outcome
Quote every custom job in 60 seconds with guaranteed profit margins built in
Problem Description
Inconsistent Job Pricing
You eyeball prices for custom prints and often undercharge
Complex designs take longer but you don’t adjust pricing accurately
Calculating material cost + machine time + labor manually takes 10+ minutes per quote
You lose money on jobs you thought would be profitable
Business Opportunity
Print Time Pricer
Upload STL file → get instant price quote with your target margin based on print time estimate, material weight, and machine costs
Idea Breakdown
Project Type
Web App
Core Feature
Analyze STL files to calculate print time and material usage, then generate price quotes with configurable profit margins
Main User Scenario
User uploads customer’s STL file
User selects material type (PLA, ABS, PETG) and current $/kg cost
User sets target profit margin (e.g., 40%)
System calculates estimated print time using slicing algorithms
System outputs final quote price with breakdown (material + machine time + margin)
Quick Start Steps
STL Analysis Engine
tools: Python + Flask (backend API), numpy-stl library (STL parsing), CuraEngine-legacy (open-source slicer for time estimates), Fly.io (Python deployment)
skills: Python file processing, 3D geometry basics, REST API design
key decisions/validations: API endpoint that accepts STL upload and returns print time + material weight; Accurately estimates print time within 15% margin for test files
Pricing Calculator UI
tools: Lovable (UI generation for calculator interface), Next.js 14 (App Router), Tailwind CSS + shadcn/ui, React Dropzone (file upload), Vercel (deployment)
skills: File upload handling, Form state management, API integration
key decisions/validations: Clean interface for STL upload + pricing inputs with instant quote display; User can upload file, adjust margins, and get quote in under 60 seconds
Quote History (Optional)
tools: Supabase (free tier - 50k MAU), PostgreSQL (via Supabase), Supabase Auth (email magic links)
skills: Database schema design, Auth integration
key decisions/validations: Save quote history for repeat customers (Supabase free tier chosen over paid Firebase - saves initial costs during validation); Users can revisit past quotes and adjust margins retrospectively; quotes_generated >= 20; returning_users >= 5
3 Reasons to Consider This Idea
Immediate value without learning curve — Works with files customers already send you—no new software to learn
Captures profit leakage instantly — Most service providers undercharge by 20-40% on complex prints; this fixes it immediately
Is This Idea For You?
✅ Basic understanding of 3D printing terminology (print time, infill, layer height)
✅ Comfortable integrating Python backend with JavaScript frontend
✅ Want to transition from guesswork to data-driven pricing
Closing Considerations
This is a quoting tool, not a full pricing engine—you still approve final prices. Start with basic slicing estimates; accuracy improves with user feedback on actual print times. Differentiation: Existing slicers (Cura, PrusaSlicer) show time but don’t auto-calculate pricing with margins. Natural expansion: save customer profiles, integrate with invoicing, add rush job multipliers.
Core Promise: Every quote you send will cover your costs and hit your target margin automatically
3. Filament Price Alert
Know the moment filament prices drop below your target margin
Target Customer
3D printing shop owners who buy filament in bulk and struggle to time purchases when prices fluctuate
The Problem
Desirable Outcome
Never overpay for filament again by buying only when prices support your profit margins
Problem Description
Unpredictable Material Costs
Filament prices change weekly across suppliers but you check manually
You buy at high prices because you didn’t know a sale started yesterday
Profit margins vanish when material costs spike unexpectedly
No way to set ‘buy alerts’ based on your specific margin requirements
Business Opportunity
Filament Price Alert
Set your target filament cost per kg → get instant email/SMS when any tracked supplier drops below that price
Idea Breakdown
Project Type
Web App
Core Feature
Monitor filament prices across suppliers and send alerts when prices drop below user-defined thresholds
Main User Scenario
User enters their target filament cost (e.g., $18/kg for PLA)
User selects suppliers to monitor (Amazon, MatterHackers, etc.)
System scrapes prices every 6 hours
When price drops below threshold, user gets email/SMS alert
User clicks through to buy at the optimal price
Quick Start Steps
Scraper + Alert Logic
tools: Node.js + Puppeteer (price scraping), Pocketbase (self-hosted on Fly.io free tier), SQLite (via Pocketbase for user thresholds), Node-cron (scheduled scraping every 6h), Resend API (email alerts - 3k/mo free tier)
skills: Web scraping, Cron jobs, REST APIs
key decisions/validations: Automated price checks with email alerts (Pocketbase chosen over Firebase to avoid $25/mo + saves 3 hours on auth setup); Script successfully scrapes 3 suppliers and sends test alert
Minimal Input UI
tools: Bolt.new (rapid UI generation), React + Vite, Tailwind CSS + DaisyUI, Pocketbase JS SDK
skills: Form handling, API integration
key decisions/validations: Simple form to set price thresholds and select suppliers; User can save threshold and see list of monitored suppliers
Deploy & Validate
tools: Vercel (frontend), Fly.io (Pocketbase + scraper), Uptime monitoring (Cron-job.org free tier)
skills: Environment variables, Cron deployment
key decisions/validations: Live scraper running every 6 hours with public signup page; 5 users set alerts; 2 receive price drop notifications within 48 hours; active_alerts >= 5; alerts_sent >= 2
3 Reasons to Consider This Idea
Solves immediate pain without workflow change — Users keep buying where they buy now—they just get notified of better timing
Clear affiliate revenue path — Every alert can include your affiliate link to the supplier offering the deal
Is This Idea For You?
✅ Comfortable with web scraping and DOM parsing
✅ Can handle basic cron job setup and monitoring
✅ Interested in affiliate or lead-gen monetization
Closing Considerations
This is NOT a full pricing engine—it’s a purchase timing tool that feeds into your pricing decisions. Start with 3-5 major suppliers; scraper can break but users will report it quickly. Natural expansion: add price history charts, multi-material support, bulk purchase calculators.
Core Promise: You’ll never miss a filament deal that protects your margins again
4. Shipment Weight Matcher
Find other sellers shipping to the same destination this week to split freight costs
Target Customer
Small-batch hardware sellers and makers shipping heavy items (5-50kg) internationally who ship 2-10 packages per month
The Problem
Desirable Outcome
Cut your international shipping costs by 40-70% by matching with other sellers heading to the same country
Problem Description
Prohibitive per-unit freight costs for low-volume sellers
You pay $80 to ship a 10kg package when bulk shippers pay $25 for the same route
Can’t compete with large sellers who get volume discounts from freight forwarders
Every quote feels like a choice between profit margins or losing the sale
You know consolidation exists but have no way to find other small shippers
Business Opportunity
Shipment Weight Matcher
Post your pending shipment (destination, weight, ship-by date) and get matched with other sellers shipping to the same region in the same timeframe to share a consolidated freight booking
Idea Breakdown
Project Type
Web App
Core Feature
Match pending shipments by destination country and timeframe, showing potential cost savings when 2+ sellers combine volumes
Main User Scenario
Seller posts: ‘Shipping 12kg to Germany, flexible dates next 2 weeks’
System shows active matches: ‘2 other sellers, total 35kg → estimated $31/package vs. $78 solo’
Seller requests match introduction (email/contact swap)
Matched sellers coordinate with same freight forwarder for pickup
System marks shipment as ‘matched’ and collects outcome data
Quick Start Steps
Core Matching Interface
tools: Bolt.new (rapid full-stack prototype), React 18 + Vite, Tailwind CSS + shadcn/ui, Lucide icons
skills: Prompt engineering for UI generation, Component customization
key decisions/validations: Working shipment posting form and match display in 3 hours using AI-generated components; User can post a shipment, see formatting validation, and view a mock match result
Lightweight Backend
tools: Pocketbase (self-hosted on Fly.io free tier), SQLite via Pocketbase, Pocketbase realtime subscriptions
skills: REST API basics, Pocketbase schema design
key decisions/validations: Persist shipment posts and enable match queries with zero monthly cost (Pocketbase vs. Firebase/Supabase saves 4 hours of auth setup + $20/mo; simple matching logic doesn’t need Postgres); New posts appear in match feed within 2 seconds; destination-based filtering works
Match Algorithm
tools: JavaScript (client-side filtering), Date-fns (date range matching), Simple scoring function
skills: Array filtering, Date calculations
key decisions/validations: Score matches by destination proximity (same country = 100pts, same region = 50pts) and date overlap; Germany + Netherlands shipments show as ‘regional match’; 14-day window catches flexible dates
Contact Exchange
tools: Email obfuscation (reveal on click), Pocketbase auth (optional, email-only), Simple match request button
skills: Email validation, Click event handling
key decisions/validations: Facilitate seller-to-seller contact without exposing emails publicly; User A requests match with User B → both get email notification with contact details
Deploy & Seed Initial Data
tools: Vercel (frontend), Fly.io (Pocketbase backend), Manual seed data (10-15 realistic posts)
skills: Environment variable management, CSV import to Pocketbase
key decisions/validations: Live site with enough sample data to demonstrate value immediately; First 5 real users see at least 2 potential matches in their destination; 1 match request made; match_requests_sent >= 1; active_shipment_posts >= 5
3 Reasons to Consider This Idea
Immediate network effect with just 10 users — Unlike marketplaces that need thousands of listings, 3-4 active shipments to Germany creates instant value
No payment processing needed for MVP — You’re just introducing sellers; they handle consolidation payment with freight forwarder directly (add take-rate later)
Viral loop built-in — Every successful match creates 2+ advocates who saved real money; word-of-mouth in maker communities is strong
Is This Idea For You?
✅ Comfortable building CRUD interfaces with modern React
✅ Can set up and deploy Pocketbase in a few hours
✅ Willing to manually seed first 20 shipment posts to bootstrap network
✅ Have access to 1-2 maker/seller communities to recruit first users
Closing Considerations
Existing freight consolidators (Flexport, Freightos) target large shippers with complex quoting—this is peer-to-peer matching for micro-volumes they ignore. Start hyper-local: focus on US sellers shipping to EU or Asia first; one route with density beats thin coverage across all routes. The 48-hour version is a matchmaking board; V2 adds freight forwarder API integration for instant quotes, V3 handles payment splitting.
Core Promise: You’ll see real consolidation opportunities with other small sellers in under 2 minutes of posting your shipment
5. Ad Spend Simulator
Test budget splits before spending a dollar
Target Customer
Small business owners about to launch their first multi-channel ad campaign or reallocate existing budget across 2-4 platforms
The Problem
Desirable Outcome
See predicted ROI for different budget split scenarios using your actual historical data or industry benchmarks, so you can commit to a strategy confidently
Problem Description
Budget allocation paralysis
You have $2,000/month to spend but no idea if it should be 50/50 or 80/20 across channels
Expensive to test splits in production—each wrong guess costs real money
Gurus say ‘test everything’ but you can’t afford months of random experiments
Every platform’s rep claims their channel should get the majority
Business Opportunity
Ad Spend Simulator
Input your total budget, upload past campaign CSVs (or use industry averages), drag sliders to test different % allocations, see projected conversions and ROI for each scenario
Idea Breakdown
Project Type
Web App
Core Feature
Calculate and visualize expected outcomes for different budget allocation strategies using historical performance data or industry benchmarks
Main User Scenario
User enters total monthly budget (e.g., $2,000)
User either uploads CSV exports from past campaigns OR selects their industry from dropdown (uses benchmark data)
System extracts CPA and conversion rates per channel from data
User drags allocation sliders to test splits (e.g., 60% Facebook, 40% Google)
System shows projected conversions, cost per acquisition, and total ROI for that split
User compares 3-4 scenarios side-by-side before making decision
Quick Start Steps
Calculation Engine + CSV Parser
tools: Bolt.new (rapid prototype with natural language), React 18, PapaParse (CSV parsing library), Lodash (data manipulation)
skills: File upload handling, Data parsing, Mathematical modeling
key decisions/validations: Working calculator that ingests CSV, extracts CPA/conversion rates, and computes ROI for any budget split; Upload sample Facebook + Google Ads CSVs; system correctly calculates projected conversions for 70/30 split
Interactive Allocation UI
tools: Lovable (AI-generated UI components), shadcn/ui sliders + cards, Recharts (stacked bar chart for scenario comparison), Tailwind CSS
skills: State management, Slider interactions, Responsive design
key decisions/validations: Drag-and-drop budget sliders with live-updating projections; side-by-side scenario cards; User can create and compare 3 allocation scenarios in under 2 minutes
Industry Benchmark Database
tools: Static JSON file (15-20 industries), Average CPA + conversion data from Wordstream/AdEspresso public reports, Fetch API
skills: Data curation, JSON manipulation
key decisions/validations: Users without historical data can select industry and get reasonable baseline projections; User selects ‘E-commerce’ industry; system populates with 2.5% avg conversion, $35 CPA for Facebook
Deploy & Share
tools: Vercel (static site), No backend needed (client-side only), URL parameter encoding (shareable scenario links)
skills: Static deployment, URL state management
key decisions/validations: Public calculator; users can share scenario URLs with team/advisors; 20 users run simulations; 5 share links with others; simulations_run >= 20; shared_scenarios >= 5
3 Reasons to Consider This Idea
Zero risk validation—helps before they spend — Unlike monitoring tools that need active campaigns, this works for pre-launch planning
Natural upsell to optimization service — After showing projections, offer ‘Done-for-you campaign setup’ or ‘Monthly reallocation service’
Viral sharing potential — Business owners will share scenarios with partners/advisors, driving organic traffic
Is This Idea For You?
✅ Comfortable with CSV parsing and data transformation
✅ Can build interactive UI with sliders and live updates
✅ Interested in content/SEO-driven acquisition (rank for ‘ad budget calculator’)
✅ Willing to research and curate industry benchmark data
Closing Considerations
This is a decision-support tool, not an automation platform—it helps humans choose, not choose for them. Existing tools like Google Ads recommendations are single-platform and biased toward spending more. AdEspresso has budget tools but they’re buried inside $100/mo SaaS; this is standalone and accessible. First version uses simple linear projections; can add ML-based predictions later if needed. Monetize via affiliate links to ad platforms, lead-gen for agencies, or freemium model ($0 for 3 scenarios, $9 for unlimited).
Core Promise: You’ll commit to a budget allocation strategy with projected ROI numbers, not guesses, in under 5 minutes
Now go build!
See ya next week,
— Ale & Manuel
PS — If you’re finding value in Ship With AI, would you mind forwarding this edition to a friend? It only takes a few seconds, but it helps me reach more tech creators and builders like you.
We’d also love your feedback to make Ship With AI even better. Please drop a comment with:
Ideas you want to see in future editions
Your biggest takeaway from this one
I read and reply to every single message!