Base44 Tutorial (2026): Build and Ship a Working Internal Tool in an Afternoon, Step by Step

Base44 tutorial: the short answer

As of September 2026, you can build a working internal tool in Base44 in about ten prompts and roughly 15 credits, inside the free plan's 25 message credits a month, and ship it to a team for $16 a month on Starter. This tutorial builds a job tracker with a form, a table, a status filter, login, permissions, and your real data imported, then tells you where builds break and when to stop. Every plan, price, and credit figure comes from base44.com/pricing and docs.base44.com, read on September 15, 2026.

I maintain 8+ Base44 apps that other people built, so I've seen what the platform does when nobody is guiding it. Most of the mess comes from four repeatable mistakes, all avoidable if you build in the order below.

What you'll build

A job tracker for a small service business: plumbing, landscaping, a two-truck HVAC shop, whatever you run. It has:

• A Jobs table with customer name, address, phone, job type, scheduled date, amount, status, and notes.
• A form to add a job, and a click-to-edit view for each one.
• A table of all jobs, newest first, with a status filter: Quoted, Scheduled, In progress, Done, Invoiced.
• Login, an admin role for the owner, and technicians who only see jobs assigned to them.
• Your existing jobs imported from a spreadsheet.

Small on purpose. The Base44 prompt guide's best advice is "build one piece at a time," and a tracker like this is the size where the platform shines. For what Base44 is and who it's for, read what is Base44 first.

Prerequisites and the plan you need

You need: a free Base44 account, a spreadsheet of your current jobs saved as CSV, and an afternoon. The free plan covers the whole build. You'll want Starter when you ship, because Base44 says "Private apps are available on paid plans only," and an internal tool with customer phone numbers in it should be Private or Workspace, not Public. The full cost story, including the credits that don't show up on the pricing page, is on Base44 pricing and is Base44 free.

Credit budget, from Base44's own ranges: the first build is a fixed "about 1 credit." After that, a simple visual change is about 0.5, a small feature about 1, a complex module about 2, an app-wide change 3 to 4. Discuss mode is 0.3 a message. Manual edits in Edit mode are free. Ten well-scoped prompts land around 12 to 15 credits.

The build, step by step

Type each prompt into the AI chat in Build mode (the default). Clicking around the live preview is free.

Step 1: The first prompt (about 1 credit)

Type: "Build an internal job tracker for a small plumbing company. One table called Jobs with these fields: customer_name (text), address (text), phone (text), job_type (text), scheduled_date (date), amount (number), status (one of: Quoted, Scheduled, In progress, Done, Invoiced), assigned_to (text, an email address), notes (text). One page called Jobs that shows all jobs in a table, newest scheduled_date first, with an Add Job button that opens a form with those fields. Calm, professional design, plenty of white space."

What Base44 generates: the Jobs entity with those fields, a Jobs page with the table and the add form, navigation, and hosting on a free base44.app URL. The docs say it handles "design, databases, signups, user permissions, and hosting" from the first prompt; in practice the first build is a rough draft you shape from here.

Step 2: Check the data model before anything else

Open Dashboard, then Data. Every table appears as a card. Open Jobs and check the field types: scheduled_date should be Date/Time, amount should be Number, status a choice, not free text. Fix it now with one prompt, because everything after this builds on the schema.

Type (if needed): "Change the status field on Jobs to a select with exactly these options: Quoted, Scheduled, In progress, Done, Invoiced. Default new jobs to Quoted."

Step 3: The status filter (about 1 credit)

Type: "On the Jobs page, add a row of filter chips above the table, one per status plus All, so it works like Trello's board filters. Show a count on each chip. Default to All. Add a search box that matches customer_name and address."

What Base44 generates: the chips, counts, and search wired to the table. Borrowing from an app people know ("like Trello") is a shortcut the prompt guide recommends, as long as you say which part you mean.

Step 4: Click-to-edit and status changes (about 1 credit)

Type: "Clicking a job row opens a side panel with all its fields editable and a Save button. Add a status dropdown in the panel and in the table row so status can be changed in one click. Add a delete button in the panel with a confirmation."

Step 5: Login and roles (about 1 credit)

Every new Base44 app already has login, register, forgot-password, and reset-password pages. This step decides who's who.

Type: "Require login for the whole app. There are two roles: Admin (the owner) and User (technicians). Admins see all jobs. Users only see jobs where assigned_to matches their email. Only admins can delete jobs or change amount."

What Base44 generates: the visibility and permission rules, using what its docs call Entity-User Field Comparison (assigned_to matched against the user's email) and User Property Check (role equals Admin). Then go to Dashboard, Settings, Authentication and enable the sign-in providers you want, such as email or Google, and click Add to pages so the button lands on the login page.

Step 6: Verify the permissions by hand (0 credits)

Open Dashboard, Data, the Jobs table, Permissions. Read the rules for Create, Read, Update, Delete. If you see a Permission risks detected banner, click Fix and read what it changed. Then use More Actions, Act as a user in the top bar to view the app as a technician and confirm they only see their own jobs. This is the step everyone skips and the one I get called about later.

Step 7: Import your real jobs (about 1 to 2 credits)

Click the Upload files icon in the chat and attach your CSV.

Type: "Import this CSV into the Jobs entity. Map the columns to the existing fields, convert dates to scheduled_date, and set status from the Status column. Show me the mapping and wait for my approval before importing."

What Base44 generates: a column mapping, then the rows. Two facts from the data docs to remember: imports "add new rows to your tables. They do not update or overwrite existing records," so a second run creates duplicates, and deleted records stay recoverable for 30 days. Export the table first if you're nervous.

Step 8: A dashboard card row (about 1 credit)

Type: "Add three cards above the filter chips: jobs scheduled this week, jobs in progress, and total amount of jobs with status Done but not Invoiced. Make the third card red if it's over $5,000."

Painting the screen gets you the layout in one round. "Make a dashboard" gets you three.

Step 9: Test like a user, then tidy in Edit mode (0 credits)

Switch to mobile view from the device menu in the top bar; a technician will use this from a truck. Then switch to Edit mode (Cmd + . on a Mac) and fix spacing, labels, and button text by clicking on them. Manual edits don't use credits and you get 50 steps of undo. If something's broken, use the Revert icon under the prompt that broke it rather than spending credits on a fix prompt.

Step 10: Publish and invite (0 credits, then $16 a month)

Click Publish in the top bar. Your app is live on its base44.app URL; rename it under Dashboard, Domains, Edit URL. Set App Visibility under Overview to Private (paid plans) or Workspace, then Send Invites with the Admin or User role for each person. To put it on jobs.yourcompany.com, connect the domain from the Domains page; Base44 says to allow up to 72 hours for DNS at an outside provider, and it handles SSL.

The four places Base44 builds go wrong, and the fix

Adding auth, a database, and a deploy: what's already there

If you came here from another tool, the surprising part of Base44 is how much of this list is pre-installed:

• Auth: login, register, forgot-password, and reset-password pages ship with every app. Providers are toggles under Settings, Authentication. SSO (Google, Microsoft, Okta) is Elite only, at $160 a month annual.
• Database: the entities you saw in Step 2, with Reference fields to link tables (a Customers table linked to Jobs is the natural next build). Import is CSV, Excel, or JSON through the chat, or CSV from the dashboard. Since November 27, 2025, data requests are limited to 5,000 items per request, which is the first hard ceiling a growing tool hits.
• Deploy: Publish is a button. The base44.app URL is free on every plan; a custom domain is Starter and up; backend functions (server-side code for anything the chat can't express) are Builder and up at $40 a month annual.

What isn't there, on any plan, is the code on your own machine as the source of truth. That's the trade you're making for the afternoon.

When to stop and rebuild properly

The job tracker above will run happily for years. The apps that end up on my desk didn't stay that size. The signals that it's time to move off Base44, in the order I usually see them:

1. The data model changes weekly. Five or six related tables with rules that keep shifting means every prompt risks breaking the last one.
2. You're writing backend functions to work around the builder. Once the important logic lives in code the chat can't see, you have a codebase without the tooling of one.
3. Customers, not staff, are logging in. An internal tool can tolerate a bad afternoon. A customer-facing product can't, and permissions mistakes stop being embarrassing and start being liabilities.
4. You hit the 5,000-items-per-request limit or the integration credits are the biggest line on the bill.

My verdict on where Base44 is the right tool, and the three things it consistently breaks on, is in the Base44 review. What a rebuild actually looks like, and what the ones that went well had in common, is on vibe coding examples. The short version: build the tracker this afternoon, run it for a quarter, and if it's become the business by then, that's the best problem an AI-built app can have.