# FORGE

> FORGE is the AI platform companies license for their whole team. Their people describe the work in plain words and get a working tool back the same day, checked at every step, and the FORGE team onboards every company itself. FORGE is made by Santiago Innovations and licensed by Fox & Santiago. It is not forge.new or any other product named Forge.

- Website: https://forge-dev.com/
- Pricing: $49 a seat a month, with 3 builds included. Build packs $150 for 10. App users $10 a month. Seats renew at one set price, and nothing extra is charged without your OK.
- Phone: (877) 244-9687
- Founder: Jason Samir Santiago (https://lettheaibesmart.com/author)
- Parent company: Santiago Innovations (https://santiago-innovations.com/)
- Guides feed (RSS): https://forge-dev.com/feed.xml

## Key pages

- [FORGE: The tools your business runs on, built by the people who do the work](https://forge-dev.com/): License FORGE for your team. Your people describe the work in plain words and get a working tool back the same day, checked at every step. Onboarded by us.
- [How FORGE works](https://forge-dev.com/how-it-works): Describe the work in plain words. A panel of top AI models plans it, an AI crew builds it, and every piece is checked before your team opens it.
- [What teams build with FORGE](https://forge-dev.com/use-cases): Dispatch boards, intake trackers, job site checklists, close checklists and more: the tools teams build with FORGE when they describe their work in a paragraph.
- [FORGE pricing](https://forge-dev.com/pricing): $49 a seat a month, with 3 builds included. Build packs $150 for 10. App users $10 a month. Seats renew at one set price, and nothing extra is charged without your OK.
- [Security and data at FORGE](https://forge-dev.com/security): Your company's apps stay yours, only invited people get in, every role sees exactly what it should, and every piece is checked for security before it is saved.
- [FORGE vs AI app builders](https://forge-dev.com/compare): Top AI models plan it, an AI crew builds it, and every piece is checked. Every tool arrives finished, with flat seat pricing. How FORGE compares, with sources.
- [Talk to us](https://forge-dev.com/talk): Tell us what your team spends too much time on. We onboard every team ourselves and build the first tools with you.
- [Guides](https://forge-dev.com/guides): 82 guides on bringing AI into a team: AI app builders, what they really cost, where they fail, and how teams put AI to work.

## Guides: Comparisons

- [AI app builders compared on roles, permissions and audit records](https://forge-dev.com/guides/ai-builders-roles-and-permissions): As listed in October 2026, Lovable, Bolt, Replit, Softr and GlideOS keep audit logs on Enterprise, v0 keeps SAML SSO and role-based access control on Enterprise, and Retool offers audit logs from Business. Price the tier that has the sign-in, role and audit controls you need, and check access inside each app, not just in the builder's workspace.
- [Airtable vs monday.com vs custom internal apps](https://forge-dev.com/guides/airtable-vs-monday-vs-custom-apps): Choose Airtable for a flexible database and monday.com for a work management board, knowing both charge for everyone who edits. Choose a custom internal app when your workflow has its own rules, approvals and field steps, and with a business AI platform like FORGE your own people build it by describing the work, with app users at $10 a month each.
- [AppSheet or Power Apps: which should a small business on Google Workspace or Microsoft 365 use?](https://forge-dev.com/guides/appsheet-vs-power-apps): A small business on Google Workspace should start with AppSheet ($5, $10 or $20 per user a month, with Core included in most paid Workspace plans), and one on Microsoft 365 should start with Power Apps (Premium is $20.00 per user a month paid yearly), knowing both charge for every person who uses an app. If your people would rather describe tools in plain words than learn an editor, FORGE is the third option, with onboarding by our team and app users at a flat $10 a month.
- [Bubble vs FlutterFlow vs AI-built apps: which fits a business team in 2026](https://forge-dev.com/guides/bubble-vs-flutterflow-vs-ai-builders): Bubble and FlutterFlow fit a business team with someone willing to learn a visual editor and assemble the app screen by screen, while AI app builders such as Lovable, Bolt, Replit and Base44 write the app from a plain-language request and meter every attempt in credits or tokens. For a team without developers, decide on who will build, how the bill grows, whether app users cost money and who checks the result for security.
- [Can non-developers vibe code business tools? Code editors, app builders and business AI platforms compared](https://forge-dev.com/guides/vibe-coding-for-non-developers): Yes, non-developers can vibe code business tools, but the kind of tool decides whether it works: AI code editors such as Cursor and Windsurf assume you can read and ship code, and AI app builders such as Lovable, Bolt, v0, Replit and Base44 leave security, fixes and the bill to whoever publishes. Business AI platforms let managers describe the work and get a checked tool with roles, a record of who did what, countable pricing and onboarding.
- [Can you take your apps and data with you when you leave an AI app builder?](https://forge-dev.com/guides/ai-app-builder-lock-in-and-export): You can leave an AI app builder cleanly only if you plan for more than exporting code: your data in a format you can use, the logic that only runs on the platform, a pricing meter the vendor can redefine, product lines that split and the knowledge in one person's head. Write the exit plan before you commit: what you would take, in what format, who would run it and what it would cost.
- [Glide vs Softr vs AI app builders for employee tools](https://forge-dev.com/guides/glide-vs-softr-vs-ai-builders): For employee tools the whole staff will use, the deciding difference is what app users cost: Softr caps logins per plan and bills extra app users on Pro and above, Glide Classic Business includes 30 users and charges $5 to $6 for each additional one, and Lovable, Bolt and Replit list no per-user charge but meter AI work in credits or tokens. FORGE pairs plain-words building with app users at a flat $10 a month and $49 builder seats with 3 builds.
- [How do I move my app off Lovable, Bolt or Replit?](https://forge-dev.com/guides/migrate-off-lovable-bolt-replit): To move an app off Lovable, Bolt or Replit, export every record first, write down what the app actually does (screens, fields, rules, roles and alerts), rebuild it on the new platform from that description, run both side by side for a week, then switch over and shut the old one down properly. For a team without developers, rebuilding from a clear description is usually faster and safer than trying to move the code itself.
- [Lovable vs Bolt vs v0 vs Replit vs Base44 for business apps](https://forge-dev.com/guides/lovable-vs-bolt-vs-replit-vs-base44): For business apps, Lovable, Bolt, v0, Replit and Base44 all build fast from a typed request, so the real differences are the meter and the controls: Lovable shares credits across unlimited members, Bolt Teams is $30 per member, v0 is $30 or $100 per user, Replit Pro covers up to 15 builders for $100 and Base44 starts at $16 a month billed annually. Audit logs sit on Enterprise at Lovable, Bolt and Replit, and on all five the person publishing the app is the one who has to check its security.
- [Managed vs self-serve AI app builders: which does a business need?](https://forge-dev.com/guides/managed-vs-self-serve-ai-app-builders): A self-serve AI app builder gives you the tool and leaves setup, security settings, roles and training to your team; a managed one adds people who onboard you, set up access, help build your first real tools and stay with you after launch. If nobody on staff owns software today, a business is usually better served by a managed platform with implementation support.
- [Microsoft Power Apps alternatives for teams that want speed](https://forge-dev.com/guides/power-apps-alternatives): The main Power Apps alternatives are AppSheet, Retool, Softr, Glide, AI builders that list no per-user charge such as Lovable, Replit and Bolt, and business AI platforms like FORGE, where people describe the tool in plain words, app users are $10 a user a month and builder seats are $49 with 3 builds. Power Apps itself fits companies deep in Microsoft 365 with someone to own the platform, with Premium at $20.00 per user per month paid yearly.
- [Retool alternatives for teams with no developers](https://forge-dev.com/guides/retool-alternatives-for-non-developers): The best Retool alternative for a team with no developers is a platform where people describe the tool in plain words and the platform checks the work, such as FORGE at $49 per builder seat with 3 builds a month, onboarding included and app users at $10 a user a month. Retool itself suits builders comfortable with data and logic, at $50 per builder and $15 per internal user a month on Business billed annually, with SSO and SCIM on Enterprise only.
- [The best AI app builders for internal business tools in 2026](https://forge-dev.com/guides/best-ai-app-builders-for-internal-tools): The best AI app builder for internal business tools keeps every app inside your company, controls who gets in, records every change and prices in a way your finance lead can forecast. Lovable, Bolt, v0, Replit and Base44 are fast but mostly keep single sign-on and audit logs on top tiers, Retool, Power Apps and AppSheet charge for the people who use the apps, and FORGE is built for teams without developers, with onboarding by our team, $49 builder seats with 3 builds and app users at a flat $10 a month.
- [The best Lovable alternatives for business teams](https://forge-dev.com/guides/lovable-alternatives-for-business): The main Lovable alternatives for business teams are Bolt, v0 and Replit for building from a typed request, Retool, Power Apps and AppSheet for internal tools that charge for app users, and FORGE for teams that want roles, a full record of every change and security checks for every team, with app users at a flat $10 a month. Compare them on private-by-default apps, roles, a record of every change, checks before anything goes live and pricing you can cap.
- [Which AI app builders charge the people who only use the apps](https://forge-dev.com/guides/ai-app-builders-that-charge-app-users): Microsoft Power Apps, Google AppSheet and Retool license each app user, Softr caps app users per plan and bills extra ones, and Glide Classic Business charges past 30 users. AI builders such as Lovable, Bolt, v0, Replit and Base44 list no per-user charge for app users, but they meter building instead.

## Guides: Bringing AI into your team

- [AI platform vs hiring a developer or freelancer in 2026](https://forge-dev.com/guides/ai-platform-vs-hiring-a-developer): For internal tools that run your own workflows, such as scheduling, approvals, checklists, tracking and dashboards, an AI platform your team uses directly is usually faster and far cheaper than hiring a developer. Hire a developer when software is your product or you need deep custom engineering, and use a freelancer for a well-defined one-off project with a clear finish line.
- [Can employees build their own internal tools without a developer?](https://forge-dev.com/guides/build-internal-tools-without-a-developer): Yes. Employees can build internal business tools without a developer by describing the work in plain words to an AI platform built for business teams, then testing the result with two or three real users before the whole team relies on it, on a platform that keeps every app inside the company, controls access by role and checks every piece for security.
- [Do I need an app or just an automation like Zapier, Make or n8n?](https://forge-dev.com/guides/app-or-automation-zapier-make-n8n): You need just an automation when the information already lives in systems you use and the job is moving it or sending a notice when something happens. You need an app when people have to see, add to or approve a shared list of work, with statuses, roles and a record of who did what, because that list has nowhere else to live.
- [How much does custom business software cost in 2026?](https://forge-dev.com/guides/what-custom-business-software-costs): Custom business software costs anywhere from a few hundred dollars a year to a full-time developer, whose median wage the BLS put at $135,980 in May 2025. Your number is set by per-user charges, credits spent on every fix, hosting, security and upkeep, so compare three-year cost for your actual builders and users and ask what a change costs before you sign.
- [How to bring AI into a team of 10 to 50 people (start with a one-department pilot)](https://forge-dev.com/guides/bring-ai-into-a-small-team): Bring AI into a team of 10 to 50 people by piloting it for about 30 days with one department, on one painful, repeated workflow, with one owner and one approved platform, measured against a baseline you take first. Once that team would refuse to go back to the old way, expand department by department using the same method.
- [How to get employees to actually use new internal software](https://forge-dev.com/guides/get-employees-to-use-new-software): Employees use new internal software when the people who do the work shaped it, it makes their own day easier within the first five minutes, and it replaces the old way on a firm date. Involve two or three real users before launch, test with real work for a week, fix the first complaints fast and retire the spreadsheet or group text it replaces.
- [How to get skeptical managers on board with AI-built tools](https://forge-dev.com/guides/manager-buy-in-for-ai-tools): Win over skeptical managers by taking their worries about quality, data safety, extra work, cost and control seriously, letting them pick the workflow and control who builds and who sees what, and starting with one small tool their team feels within a week. Measure the result against a baseline they agree with, because a skeptic who sees their own numbers improve often becomes your best champion.
- [How to measure the ROI of employee-built internal tools](https://forge-dev.com/guides/roi-of-employee-built-tools): Measure the ROI of an employee-built tool as hours saved times a loaded hourly cost, plus errors and delays avoided, minus what the tool really costs in seats, builds and the staff time spent building and training. Take a baseline before launch, measure the same way at 30 and 90 days, and count only savings the team would notice if the tool disappeared.
- [How to replace spreadsheets, email and texts with internal apps](https://forge-dev.com/guides/replace-spreadsheets-with-internal-apps): Replace a spreadsheet with an internal app once several people edit it and it drives handoffs or approvals: map the workflow, give each piece of information one home in the app, run the app alongside the sheet for a week, then switch over on a set date and close the old sheet, email and text channels. You do not need an ERP to do it; move one workflow at a time.
- [How to use AI safely without an IT department](https://forge-dev.com/guides/ai-without-an-it-department): You can use AI safely without an IT department by choosing a platform that does the IT work for you (every app kept inside the company, invite-only access with roles, security checks before anything is saved, a full record and spending caps) and naming one person to own a short set of rules. Those rules are a one-page policy, simple data rules, an app register and a one-hour quarterly review.
- [Mistakes owners make when their team starts building with AI](https://forge-dev.com/guides/mistakes-owners-make-with-ai-tools): The most common mistakes are letting people build in personal accounts, skipping roles and access rules, letting AI work directly on live data, starting with the hardest workflow, choosing unpredictable usage billing, paying for every person who only uses the apps, and never switching off the old way. Each is avoided with decisions made before anyone builds: one company workspace, invite-only access with roles, checks on every piece, caps on spending and a set switch date.
- [Should you build or buy your business software, or build it with AI?](https://forge-dev.com/guides/build-vs-buy-vs-ai): Buy when your process matches everyone else's and a mature product already does it well, hire a developer when the tool is core to what you sell and you can fund ongoing maintenance, and build with AI on a business platform when the workflow is specific to your company and the people who do the work can describe it. Most small and mid-size companies end up using all three, each for the right job.
- [The first five internal tools a small business should build](https://forge-dev.com/guides/first-internal-tools-to-build): The first five internal tools most small businesses should build are a work intake and tracking board, an approval workflow, an inspection or checklist app with photos, an equipment or inventory log, and a dashboard built from the spreadsheets you already keep. They pay off first because they replace daily spreadsheet, email and group-text work, involve several people and are low risk to test.
- [What happens to AI-built tools when the person who built them leaves](https://forge-dev.com/guides/when-the-app-builder-leaves): When an employee who built AI tools leaves, those tools often leave with them or stop working, because they were built in a personal account, paid for on a personal card or understood by only one person. Prevent it by making every tool the company's from the start: built in a company workspace, with an owner, roles, a record of every change and an offboarding step that ends access in one action while the tools stay.
- [What real onboarding for an AI platform should include](https://forge-dev.com/guides/ai-platform-onboarding): Real onboarding for an AI platform should include a workshop that maps the workflows costing your team the most time, roles, access and budget caps set up before anyone builds, a first real tool built with your people on day one, short training on each person's part, and a month of follow-through to measure results and pick the next tool. A login, a video library and a help center are not onboarding.

## Guides: Security and risk

- [Are AI app builders secure? How AI-built apps expose customer records](https://forge-dev.com/guides/how-ai-built-apps-expose-customer-data): AI app builders are only as secure as the protections the platform enforces for you: AI-built apps have exposed customer records through missing rules on who can read the data, sign-in that can be skipped, passwords and keys left inside the app, and internal apps published to the open internet. Choose a platform that keeps every app inside your company, lets in only invited people with defined roles, checks every piece for security before it is saved and records who did what.
- [Are AI-built apps HIPAA, SOC 2 and GDPR compliant?](https://forge-dev.com/guides/compliance-for-ai-built-apps): No tool makes your apps HIPAA, SOC 2 or GDPR compliant on its own: compliance comes from what data your apps hold, who can reach it, your contracts with vendors and your own processes. Before building any tool with regulated data, decide what data goes in, confirm the vendor's commitments in writing and review the plan with your compliance advisor.
- [Do AI app builders train on your business data?](https://forge-dev.com/guides/does-ai-app-builder-train-on-your-data): Whether an AI app builder trains on your data is set by its terms, which vary by vendor and sometimes by plan, so get a written answer for the exact plan you buy. Get the same in writing on how long your data is kept, which outside companies receive it, who can see it and how you get it back or delete it.
- [How do I back up and roll back an AI-built app?](https://forge-dev.com/guides/ai-app-backups-and-rollback): To back up and roll back an AI-built app, know how to return the tool to a version that worked (rollback) and how to restore the data to a point before something went wrong (a backup restore), and try both before your team relies on it. Keep your own regular export of the most important records, and choose a platform that records every change so you always know what to roll back.
- [How to evaluate an AI platform before you sign](https://forge-dev.com/guides/ai-platform-due-diligence-checklist): Before you sign with an AI platform, check eight things: how it protects your data, how people join and leave, what record it keeps of every change, how it checks what the AI builds, how predictable the bill is, whether you can take your work with you, what onboarding and support you get, and how the vendor handled past incidents. Get written answers for the exact plan you will buy, because many platforms keep the governance features you need on the most expensive tier.
- [How to test an AI-built app before your team relies on it](https://forge-dev.com/guides/test-an-ai-built-app-before-launch): Test an AI-built app the way your team will use it: run real scenarios with test records, check every number by hand, sign in as each role, try it on your team's phones and feed it odd and missing inputs, then pilot it with a few people for one or two weeks before everyone switches. Write down what passing looks like first, and keep real customer records out until the access checks pass.
- [Role-based access for employee-built apps, explained simply](https://forge-dev.com/guides/role-based-access-for-employee-apps): Role-based access means each person's role, not their individual settings, decides what they can see and do, and employee-built apps need it at two layers: the platform (who can build, manage people or only use tools) and inside each app (a technician sees their own jobs, a manager sees the whole team). Design roles around real jobs, give each only the access it needs, and sign in as every role to test before real data goes in.
- [Shadow AI: when employees build apps without permission](https://forge-dev.com/guides/shadow-ai-employee-built-apps): Shadow AI is employees using AI tools, or building apps with them, without the company knowing or approving, and Pax8 found 35% of AI-engaged small and mid-size businesses discovered it in the past six months. Rather than banning it, find what already exists without punishing anyone, then give people an approved way to build that keeps every app inside the company, controls who gets in and records who did what.
- [When an AI agent deleted a production database: what happened and how to prevent it](https://forge-dev.com/guides/ai-agent-deleted-production-database): Yes. In July 2025, Fortune reported that an AI coding agent on Replit wiped SaaStr's live database, holding records on more than 1,200 executives and over 1,190 companies, during a code freeze, and you stop that by keeping AI building work separate from live data, limiting who can change tools, recording every change and confirming you can recover before you need to.
- [Which AI app builders put SSO and audit logs behind an enterprise plan?](https://forge-dev.com/guides/sso-audit-logs-enterprise-plan): As listed on vendor pages in October 2026, most AI app builders keep single sign-on, audit logs or both on Enterprise: Bolt, v0, Replit, Base44, Glide and Softr put SSO on Enterprise, and Lovable starts SSO at Business but keeps audit logs and SCIM on Enterprise. Retool offers audit logs from Business, Airtable lists SAML SSO from Business, and Cursor includes SSO on Teams, so price the plan that has the controls you need, not the plan on the banner.
- [Who is responsible when employee-built software breaks?](https://forge-dev.com/guides/who-is-responsible-when-employee-software-breaks): Responsibility is shared: the platform vendor answers for its own systems, though many vendors' terms put the data inside your apps on you, and the company owns the data, the decisions and the people. Write it down before anything breaks, with a named business owner, a builder and an admin for each tool.

## Guides: Tools by industry

- [Can clinics build their own internal apps safely?](https://forge-dev.com/guides/healthcare-internal-apps-safely): Yes, clinics can build their own internal apps safely when they decide first what each app may hold, keep patient information to the minimum, restrict access by role, record every change and confirm privacy obligations with a compliance advisor before patient information goes in. The safest start is tools that hold no patient information, such as staff schedules, supply orders and equipment checks.
- [How do agencies track client approvals and deliverables?](https://forge-dev.com/guides/agency-client-approval-tracker): Agencies track client approvals by giving every deliverable one record with an owner, a due date and a status, routing each version through internal review to the right client approver, and recording who approved which version and when. Revision rounds count against scope, and overdue feedback is chased automatically.
- [How do clinics track patient intake and follow-ups?](https://forge-dev.com/guides/clinic-intake-follow-up-app): Clinics track intake and follow-ups with an internal staff tool that lists every new patient's intake steps, such as forms, insurance verification and records requests, and every follow-up that is due, such as callbacks, lab result calls and referral checks, each with an owner and a due date. Keep patient details to the minimum each task needs, and confirm privacy obligations with your compliance advisor before any patient information goes in.
- [How do I see which agency clients are actually profitable?](https://forge-dev.com/guides/agency-profitability-dashboard): To see which clients actually make money, bring time entries, scope, budgets and fees together for every client and project, so hours used against hours sold, effective hourly rate, scope changes and margin show up while the work is still running. That takes a fast way to log time, a budget for each project and a cost rate for each role.
- [How does a small business track who owes money (an AR tracker)?](https://forge-dev.com/guides/accounts-receivable-tracker): A small business tracks who owes money with an accounts receivable tracker: one list of every open invoice with the customer, amount, due date, days overdue, the last contact and the next follow-up date, grouped into aging buckets. Each overdue invoice gets an owner and a follow-up step on a fixed schedule, and promises to pay and disputes are logged so nothing is chased twice or forgotten.
- [How does a small practice track prior authorizations?](https://forge-dev.com/guides/prior-authorization-tracker): A small practice tracks prior authorizations by logging every request in one shared queue with the patient, payer, service, codes, date submitted, reference number and status, then following up on a fixed schedule until a decision arrives and recording the approval number and dates. Denials move to an appeal step with their own deadline, and nothing is scheduled until the authorization is approved and in date.
- [How should a small law firm track intake, conflicts and matters?](https://forge-dev.com/guides/legal-intake-matter-tracker): A small firm should track intake and matters in one workflow: every inquiry captured in one form, a conflict check against past and current parties before anyone gives advice, the engagement decision and signed agreement recorded, and each matter followed through its stages with owners, key dates and tasks. It runs alongside the systems the firm already uses for documents and billing.
- [How to build a budget vs actual dashboard from your spreadsheets](https://forge-dev.com/guides/budget-vs-actual-dashboard): To build a budget vs actual dashboard, load your budget once, map each budget line to your chart of accounts, and bring in actuals from your accounting system each month so every department, location and account shows its variance in dollars and percent, its trend and a comment from the person responsible. Give each manager their own view, and the monthly spreadsheet rebuild becomes a refresh.
- [How to build a field service dispatch board without coding](https://forge-dev.com/guides/field-service-dispatch-board): To build a dispatch board without coding, describe your jobs, statuses, roles and rules in plain words to an AI platform built for business teams, and you get one shared screen of every open job, technician and appointment window that technicians also see on their phones. Roll it out to one dispatcher and a few technicians before the whole crew.
- [How to build a multi-location store audit and task app for your stores](https://forge-dev.com/guides/retail-store-audit-app): To run store audits across locations, use one tool with a scored checklist on a phone, required photos, an automatic follow-up task for every failed item and a dashboard that ranks every store. Build it around your own standards, and measure it by how fast failed items get fixed, not by how many audits get filed.
- [How to build a nonprofit grant tracking and reporting app](https://forge-dev.com/guides/nonprofit-grant-tracker): To build a grant tracker, give every funder, application, award, deadline, restricted budget and report one home, with reminders that reach the right person well before anything is due. Organize it around your grant lifecycle from prospect to closeout, tie spending to each award, and judge it by on-time reports.
- [How to build a quote approval and sales-to-operations handoff app](https://forge-dev.com/guides/quote-approval-sales-handoff): To get quote approvals and the sales handoff right, build quotes from your price list, route any discount or low-margin quote to the right approver, and turn every won quote into a complete job packet that operations accepts before work is scheduled. Judge it by quote turnaround and fewer jobs that start with missing information.
- [How to build a sales commission tracker that replaces the spreadsheet](https://forge-dev.com/guides/sales-commission-tracker): To replace the commission spreadsheet, store each salesperson's plan as written rules, bring in closed deals and payments, and let the tracker calculate commission, including splits, tiers and clawbacks, with a line-by-line statement every rep can check before payroll. Add a monthly review and approval step and a dispute process, and measure days to close commissions.
- [How to build a sales lead assignment and follow-up tracker](https://forge-dev.com/guides/sales-lead-follow-up-tracker): To make sure every lead gets followed up, capture leads from your website, phone, email and referrals in one place, assign each to the right salesperson by rule, set the next follow-up automatically and alert a manager when a lead sits untouched. Measure speed to first contact and how many leads reach a quote.
- [How to build a school device checkout and permission workflow app](https://forge-dev.com/guides/school-device-checkout-app): Schools track device checkout by scanning a tag on every laptop, tablet, hotspot and charger to record who has it, whether the family signed the agreement, its condition at each handoff, and every repair or loss. A digital permission step for families and condition records at checkout and return replace paper slips and the end-of-year scramble.
- [How to build a school maintenance and facilities request tracker](https://forge-dev.com/guides/school-facilities-request-tracker): Schools track maintenance requests by giving every teacher and staff member one simple form to report a problem and giving the facilities team a prioritized work order queue with photos, locations, assignments and status updates that go back to the person who asked. Set clear priorities by building and room, and measure time to fix and repeat requests.
- [How to build a volunteer scheduling and hours tracking app for your nonprofit](https://forge-dev.com/guides/volunteer-scheduling-app): To schedule volunteers and track hours, give volunteers one place to see open shifts, sign up in a few taps, get reminders and check in, and give your coordinator one place to fill gaps and report hours. Judge it by fewer no-shows and hours reports that take minutes instead of days.
- [How to build an accounts payable and invoice approval workflow](https://forge-dev.com/guides/accounts-payable-approval-workflow): To set up invoice approvals, bring every vendor invoice into one queue, route each one to the right approver by amount, department or vendor, and check for duplicates and missing purchase orders before approved invoices go to your accounting system for payment. Your accounting system stays the books of record, and the workflow is judged by days to approve and late fees avoided.
- [How to build an employee onboarding and equipment tracker](https://forge-dev.com/guides/employee-onboarding-tracker): To build an employee onboarding tracker, start a role-based checklist the moment an offer is accepted, assign each task to the right person in HR, IT, payroll and the hiring team with due dates set from the start date, and log every laptop, phone, key and badge issued. Follow the new hire through training to day 90, then run the same tracker in reverse for offboarding so nothing walks out the door.
- [How to capture proof of delivery and track driver routes](https://forge-dev.com/guides/proof-of-delivery-app): To capture proof of delivery, give drivers a phone app that lists their stops in order and records a signature, photos, the name of the person who received it, the time and location, and any exceptions at each stop. Dispatch builds and watches the day's routes on one board, so disputes are settled with a record instead of a memory.
- [How to capture technician job reports, photos and sign-offs on a phone](https://forge-dev.com/guides/technician-job-report-app): To capture technician job reports, give each job one phone form with a checklist for the work type, required before and after photos, parts used, notes and the customer's sign-off, saved to the job the moment the technician taps complete. Test it with a few technicians on real jobs before the whole crew.
- [How to check in shipments and inspect returns at the warehouse dock](https://forge-dev.com/guides/warehouse-receiving-returns-app): To check in shipments and returns, have the dock team receive each shipment against its purchase order on a phone, recording shortages, overages and damage with photos, and inspect every customer return to a set grade and disposition. Discrepancies route to purchasing or customer service automatically.
- [How to connect your business systems without a full ERP](https://forge-dev.com/guides/connect-business-systems-without-erp): Connect your business systems without an ERP by choosing one system of record for each kind of information, giving shared records like customers, jobs and products one ID everywhere, and building small hub apps that pull the pieces together for the people who need them. Start with the handoff that causes the most retyping, prove it, then connect the next one.
- [How to log construction daily reports from the jobsite](https://forge-dev.com/guides/construction-daily-report-app): To log daily reports from the jobsite, give the superintendent or foreman a phone app that walks through the same sections every day (weather, crews and headcount, hours, work completed, equipment, deliveries, inspections, delays, safety notes and photos) and sends the report to the office the same evening. Start by listing the sections your report needs and who reads it, because that list is the request a business AI platform builds the app from.
- [How to manage PTO requests, shift swaps and availability in one app](https://forge-dev.com/guides/pto-shift-swap-app): To manage time off and shift swaps, give people one place to request PTO, offer and pick up shifts and keep their availability current, and let managers approve with full coverage in view. It needs request forms, a coverage calendar, approval rules by role, balances, notifications and a record of every decision.
- [How to prove SOP and quality checklists were actually done](https://forge-dev.com/guides/sop-quality-checklist-app): To prove SOP and quality checklists were done, put each procedure on a phone or tablet as step-by-step checks that require proof as people work: a photo, a reading, a signature or a pass or fail with a reason. Failed items open a corrective action with an owner and a due date, and managers see completion and failure rates across every shift and site.
- [How to run a month-end close checklist your team actually finishes](https://forge-dev.com/guides/month-end-close-checklist): Run a month-end close your team actually finishes by turning it into a recurring checklist where every task has one owner, a due day counted from month-end, a reviewer for anything that touches the numbers, and a place to attach the backup. Show everyone the same live view of what is done, late or blocked, and do not call the month closed until every reconciliation is reviewed and the controller signs off.
- [How to run move-in and move-out inspections and rental turnovers](https://forge-dev.com/guides/rental-turnover-inspection-app): To run move-in and move-out inspections, walk the inspector room by room through each unit on a phone, record every item's condition with photos and notes, and compare the move-out to the move-in so damage beyond normal wear is clear. The findings become a turnover task board for cleaning, paint and repairs, and the record backs every deposit decision.
- [How to run restaurant line checks and opening and closing checklists](https://forge-dev.com/guides/restaurant-line-check-closing-checklist): To run line checks and opening and closing checklists, put each shift's checklist on a phone or tablet that records real temperatures against safe ranges, product quality and setup and breakdown steps, with a time stamp, the name of who did it and photos where proof matters. Anything out of range requires a corrective action and alerts the manager on duty.
- [How to set up purchase requests and approvals for a growing company](https://forge-dev.com/guides/purchase-request-approval-app): To set up purchase approvals, give every employee one request form, route each request to the right approvers by amount, department and category, check it against budget, and approve new vendors before anyone pays them. Approved requests become purchase orders, so finance sees committed spending before the invoice lands.
- [How to track employee certifications and license expirations](https://forge-dev.com/guides/employee-certification-expiry-tracker): Track employee certifications and license expirations by giving every credential one record with the employee, credential type, number, issue date, expiration date and a copy of the card, then sending reminders to the employee and their manager well before each date. Tie the record to scheduling, so nobody whose required credential has lapsed can be assigned to work that needs it.
- [How to track equipment maintenance and inspections](https://forge-dev.com/guides/equipment-maintenance-tracker): To track equipment maintenance, give every machine, vehicle and tool one record with its schedule, inspection checklist and repair history, and have the tracker alert the right person before anything comes due. List your equipment types, the checks each one needs and how often, and who is responsible, and you have the plain-words request an AI platform builds it from.
- [How to track machine downtime and scrap on the plant floor](https://forge-dev.com/guides/manufacturing-downtime-log): To track machine downtime and scrap, have operators log every stop and every scrapped part at the machine in a few taps, with the machine, the time, a reason from a set list and a note or photo. Reports then rank the reasons by lost time and lost parts, so the plant fixes the causes that cost the most first.
- [How to track punch lists and safety inspections on the jobsite](https://forge-dev.com/guides/construction-punch-list-safety-app): To track punch lists and safety inspections, log each item on a phone with a photo, its exact location and the responsible trade, assign it, and follow it until it is fixed and verified. Safety inspections run from a checklist in the same app, hazards reach the right person immediately, and every correction stays on record.
- [How to track restaurant inventory, waste and food cost](https://forge-dev.com/guides/restaurant-inventory-waste-tracker): To track restaurant inventory and waste, count stock on a phone in the order you walk your storage, log every item thrown out with a reason at the station, and review food cost and waste by item each week. Start with one shift, then bring in the whole kitchen.
- [How to track retail inventory and know what to reorder](https://forge-dev.com/guides/retail-inventory-reorder-app): To know what to reorder, give every product a stock count by location, a reorder point and a reorder quantity, and let the app flag what is running low and turn it into draft purchase orders by vendor for a manager to approve. Staff count by section on their phones, receive deliveries against the order and log damage and shrink with a reason.
- [How to track RFIs, submittals and change orders in one log](https://forge-dev.com/guides/construction-rfi-change-order-tracker): To track RFIs, submittals and change orders, keep all three in one numbered log where every item shows who it is waiting on, its due date, the response, and the cost and schedule impact. Roll it out on one project with your project manager before using it company wide.
- [How to track subcontractor certificates of insurance and lien waivers](https://forge-dev.com/guides/certificates-of-insurance-lien-waiver-tracker): Track subcontractor paperwork by giving each sub one record with their certificate of insurance, policy dates and limits, W-9 and any required endorsements, and logging a lien waiver against every payment on every job. Then have the tracker remind subs before a policy expires and hold a payment until the matching waiver and a current certificate are on file.
- [How to track tenant maintenance requests and dispatch vendors](https://forge-dev.com/guides/property-maintenance-request-tracker): To track tenant maintenance requests, give tenants one way to report a problem with photos, sort every request in a triage queue by urgency and property, and assign it to staff or an outside vendor with access notes, approval limits and due dates. Each request is then tracked to completion with photos, costs and tenant confirmation.

## Guides: Pricing and cost

- [How to avoid surprise AI software bills and runaway credits](https://forge-dev.com/guides/prevent-surprise-ai-software-bills): Avoid surprise AI software bills by choosing pricing your finance lead can forecast in one sentence, setting a hard cap with alerts at 80 and 100 percent, and confirming nothing beyond the plan is charged without your OK. Most surprises come from credits or tokens the AI burns on its own retries and fixes, charges for every person who opens an app, and overages that bill automatically.
- [What AI app builders really cost a 10-person team](https://forge-dev.com/guides/real-cost-ai-app-builders-10-person-team): For a 10-person team where 3 people build and 7 only use the apps, listed base prices in October 2026 run from about $25 a month for a shared-credit AI builder to $255 or more for platforms that charge every app user. The real cost is usually higher than the base price, because credits and tokens vary with how hard the AI works and security features often sit on higher plans.

## Optional

- [Terms of Service](https://forge-dev.com/terms): The terms for using FORGE, the AI platform companies license so their people build the tools they need. Licensed by Fox & Santiago.
- [Privacy Policy](https://forge-dev.com/privacy): How FORGE collects, uses and protects information, and the choices you have about your data.