# Ship a useful tool on Replit in 90 minutes: the AI build for non-coders Source: https://getstartedwithai.net/tutorials/replit-ai-non-coder-build Site: Get Started With AI Tagline: Build AI automations that actually run your business. Audience: solo professionals, freelancers, consultants and AI implementers in training Contact: hello@getstartedwithai.co.uk This Markdown companion is generated from the prerendered page for AI crawlers. # Ship a useful tool on Replit in 90 minutes: the AI build for non-coders A working internal tool, deployed and serving a few hundred users, ships from a single browser tab in under an hour. Replit Agent is the 2026 vibe-coding tool that goes furthest for non-coders: it generates the React or Python code, deploys it, and runs the database and the hosting. This tutorial covers the 60-minute build pattern that ships a real internal tool without writing a line of code yourself, plus the line where Replit Agent stops being the right pick and Cursor or Lovable take over. ## Prep before you build (5 minutes) - A Replit account at replit.com. Core plan from about £16 a month annual covers the AI usage and deploys. - A clear single-feature tool idea. "A team form for booking annual leave" works. - A working browser. Replit runs entirely in-browser. - 60 minutes uninterrupted. ## When Replit Agent is the right tool - Internal tools, prototypes and side projects up to a few hundred users. - Apps where you want code, deploy and database all from one panel. - Quick admin tools where you trade flexibility for speed of build. - Not yet right for production SaaS at scale, customer-facing high-traffic apps, or anything with strict security requirements. ## Pricing in April 2026 - Free: limited Agent usage, basic Repls. Good for one trial build. - Core at £12 a month: full Agent access, faster builds, custom deploys. - Teams at £30 per seat per month: shared Repls and team features. - Most solo professionals start on Core; the Free tier runs out of Agent credits inside the first build. ## Step 1: Brief the build (10 minutes) 1. Open replit.com and click Create Repl. 2. Choose Replit Agent. Type the brief: "Build a small internal tool for my team to book annual leave. Each user signs in with email. They request dates and a reason. Managers approve or decline. Show a calendar view of approved leave." 3. Replit Agent plans the project: framework choice (Next.js or Flask), database tables, auth and deploy. 4. Approve the plan. Replit writes the code, sets up the database, and deploys. ## Step 2: Test the first build (10 minutes) 1. Open the deployed URL Replit gives you. 2. Sign up as Manager A and Employee B. Confirm the auth works. 3. Submit a leave request as Employee B. Confirm Manager A sees it pending. 4. Approve the request. Confirm Employee B sees the status update. 5. If anything is broken, paste the error back into Agent. It usually fixes inside two iterations. ## Step 3: Iterate the design (15 minutes) - Refine: "Add a colour-coded calendar view at the top of the manager dashboard." - Improve UX: "When the calendar is empty, show a friendly empty state." - Add a feature: "Email the manager when a new request is submitted using the built-in email integration." - Each prompt is a credit. A 60-minute build typically uses 15 to 25 credits on Core. ## Step 4: Connect the data (10 minutes) - Replit includes a Postgres database by default. Agent wires the schema. - Open the Database tab. Confirm the tables match what you briefed (users, requests, approvals). - Add seed data manually if you want test users. Or prompt Agent: "Add three test users with sample requests." - Optional: connect a Google Sheet using the Sheets integration if the team already runs leave there. ## Step 5: Deploy and share (10 minutes) 1. Click Deploy. Replit uses your default replit.app subdomain or a custom domain on Core. 2. Set the deploy as Always-on so the app does not sleep. 3. Test the live URL on a phone and a different browser. 4. Send the URL to the team with the test users to log in. 5. Watch the Replit Logs panel for any errors during the first day of use. ## When Replit Agent stops being the right tool - When the user count crosses 500 active monthly. Replit hosting is fine but not optimised for scale. - When the app needs strict security audit (SOC2, HIPAA). Move to a real codebase on AWS or Vercel. - When you need granular control over the hosting (custom domains with HSTS, multi-region). Cursor plus Vercel wins here. - When the project graduates beyond internal tools. Export to GitHub and continue in Cursor. ## What you ship A signed-in internal tool live at a Replit URL. Postgres-backed records the team can update. About a day of contractor time saved on a project that previously needed a developer to set up the framework and the deploy. ## What to build next Pair this with the Lovable tutorial when the build needs Supabase and a more polished front-end, and the Cursor for non-coders tutorial when the project graduates from Replit to a developer-managed codebase. ## Related builds More tutorials in Vibe Coding. Each one runs in 60 to 90 minutes and ships a finished asset. ### Ship a small client tool in 90 minutes: the Cursor build for non-coders 60 to 90 minutes. Solo Pro. [Open tutorial](/tutorials/cursor-for-non-coders-90-min) ### Ship code changes in a day, not a week: the practitioner Claude Code build 60 to 90 minutes. Solo Pro / Implementer. [Open tutorial](/tutorials/claude-code-practitioner-guide) ### Ship a working app in an afternoon: the Lovable build 90 minutes. Solo Pro / Implementer. [Open tutorial](/tutorials/lovable-ship-app-in-afternoon) ### Demo a client-facing tool in an hour: the Bolt.new prototype build 90 minutes. Implementer. [Open tutorial](/tutorials/bolt-new-prototype-client-tools) ## Questions people ask before they start ### Do I need to know how to code? No. Replit Agent writes the code and deploys it. You read the proposed plan and the diffs to confirm they match the brief, but you do not write any of the code yourself. ### Can the app handle real users? Yes for internal tools and prototypes up to a few hundred users. Past that, plan to migrate. Replit Always-on covers most loads. ### How does Replit compare to Lovable and Cursor? Replit gives you the deepest single-pane experience (code, deploy, database all together). Lovable wins for Supabase-backed apps. Cursor wins for projects that need an IDE and a real codebase. ### Can I export the code if I outgrow Replit? Yes, push to GitHub from inside Replit and continue in Cursor or any IDE. The code is real React or Python in real files. ### How much should I charge for a Replit build for a client? A one-day Replit build with internal tool deployment runs £1,000 to £3,500. Scope tightly: one feature, one user journey.