From email, texts and spreadsheets to one workflow, without an ERP

Walk into most companies of 10 to 100 people and ask how a job, an order or a request moves from start to finish. The honest answer usually sounds like this: "The customer emails Maria, Maria puts it in the spreadsheet, she texts the crew lead, the crew lead texts back when it is done, and then someone updates the spreadsheet, usually." Every step works. The whole thing leaks.

Information gets copied by hand from one place to another. Updates live in someone's phone. The spreadsheet is always a little behind. Nobody can answer "where is this?" without asking someone. When the company grows, someone says the word ERP, and everyone flinches at the cost and the year-long project.

There is a middle path. This guide shows how to take one workflow at a time out of email, texts and spreadsheets and into a single tool your team actually uses, without buying an ERP.

What scattered work really costs

The cost hides in small moments: the copy-paste, the "did you get my text," the double booking, the quote that sat in an inbox over the weekend. Research on office work shows how much those moments add up. Asana's Anatomy of Work research reports that workers spend 60% of their time on "work about work," the chasing, status-checking and coordinating around the actual job. Zapier's survey of businesses with up to 250 people found repetitive tasks take an average of 17.3 hours a week.

In a scattered workflow, the specific costs are:

• Re-entry. The same details typed into an email, a spreadsheet, a text and an invoice.
• Status hunting. Managers calling or texting to ask where things are.
• Lost items. Requests that sit in one person's inbox or phone while they are out.
• Version confusion. Three copies of the spreadsheet, each a little different.
• No record. When something goes wrong, nobody can see who did what and when.

Why an ERP is often the wrong answer for a smaller company

An ERP solves these problems by putting everything into one large system. For a company with complex inventory, many locations and a finance team, that can be the right call. For many smaller companies, it is more than the problem needs:

• It replaces everything at once. Your accounting, inventory and operations change together, and the project takes months.
• It makes you work its way. ERPs come with their own model of how a business runs. Fitting your workflow into it often means changing a process that worked.
• It needs specialists. Setup and changes often require consultants.
• It does not fix the texting. Field crews and office staff keep texting if the ERP screen is slower than a text.

The alternative is to fix the workflows that hurt, one at a time, with tools shaped around how your team already works, and connect them as you go.

The method: one workflow at a time

Step 1: Map the workflow as it really runs

Sit with the people who do the work. Write every step, in order, and next to each step write where the information lives at that moment: an email, a text thread, a spreadsheet tab, a paper form, someone's memory.

Example: a commercial cleaning company maps its "new site request" workflow:

1. A client emails the account manager asking for an extra cleaning. (Email.)
2. The account manager checks the crew calendar. (Spreadsheet.)
3. The account manager texts the crew lead to ask if a crew is free. (Text.)
4. The crew lead replies. (Text.)
5. The account manager confirms with the client. (Email.)
6. The crew does the job and texts a photo. (Text.)
7. The office adds it to the month's invoice. (Spreadsheet.)

Seven steps, three channels, four copies of the same details.

Step 2: Decide where each piece of information lives

For every piece of information in the workflow, pick one home. Not "the spreadsheet and the email." One.

Step 3: Design the tool around the workflow

A good workflow tool has six parts. Describe each in plain words before you build.

1. A front door. One way for requests to come in: a form, a shared address that creates a record, or office staff entering calls.
2. Statuses. The stages an item moves through, such as new, scheduled, in progress, done, invoiced.
3. Roles. Who can create, assign, update and close items, and who can only view.
4. Notifications. Who gets told at each step, and how: a phone notification for the crew, an email for the client.
5. One record. Every item has one page with its full history.
6. Views for each person. The crew sees today's jobs. The account manager sees open requests. The owner sees the week.

Step 4: Build it with the people who do the work

The account manager, a crew lead and the office person who invoices should be in the room. They know which details matter and which steps can be skipped. Build the smallest version that replaces the whole workflow. A tool that handles five of the seven steps leaves two steps on text, and the texting comes back.

Step 5: Switch over and close the old channels

1. Pick a switch date and tell everyone.
2. Import open items from the spreadsheet so nothing is lost.
3. Make the spreadsheet read-only and archive it.
4. Reply to texts and emails with the link for the first two weeks. "Please put that in the request tool so the crew sees it."
5. Fix friction daily for the first week.

Step 6: Move to the next workflow, and connect them

Once the first workflow runs in its tool, pick the next one, preferably one that shares a handoff with the first. In the cleaning example, invoicing is the natural next step. Use the same client, site and crew lists, so a completed request flows into invoicing without retyping. Over a few months you get much of what an ERP promises, built in the shape of your business.

Workflows that usually live in email, texts and spreadsheets

If you are not sure where to start, these are the workflows that most often run across scattered channels in smaller companies. Each one makes a good single tool.

• Service and job requests: a customer asks, someone schedules, a crew does it, the office bills it.
• Purchase requests and approvals: someone needs something, a manager approves, someone orders, someone receives.
• Invoice approvals: a bill arrives by email, gets forwarded for approval, gets paid, gets filed.
• Time off and shift swaps: requests by text, approvals by text, a calendar nobody trusts.
• Customer intake: a call, an email or a web form, then a spreadsheet row and a follow-up someone has to remember.
• Inspections and checklists: paper forms or photos in a group chat, retyped later.
• Maintenance requests: a tenant, a site or a machine needs attention, and the request bounces between people.

Look for the one that generates the most "where is this?" questions. That is where one tool returns the most time, and where the team will feel the difference in the first week.

Comparing the options

Prices below are from each vendor's own pages as listed in October 2026.

The right choice depends on who will build and how many people will use the tool. When a crew of thirty uses a tool that two people build, the cost of each app user matters more than the builder seat.

Mistakes to avoid

• Building half the workflow. Every step left on text pulls the team back to text.
• Keeping the spreadsheet "just in case." Two sources of truth means none.
• Designing for the office only. If the field crew cannot update from a phone in seconds, they will text.
• Notifying everyone about everything. People stop reading. Notify the person who needs to act.
• Trying to do every workflow at once. That is the ERP project again, by another name.

Checklist

1. Pick the workflow that creates the most texts and emails each day.
2. Map every step and where its information lives today.
3. Choose one home for each piece of information.
4. Describe the front door, statuses, roles, notifications, record and views.
5. Build with the people who do the work, covering the whole workflow.
6. Import open items and archive the spreadsheet as read-only.
7. Switch on a set date and redirect old channels to the tool.
8. Fix friction daily for the first week.
9. Measure time per item and items waiting before and after.
10. Pick the next workflow that shares a handoff, and reuse the same lists.

How FORGE handles it

FORGE turns a scattered workflow into one tool, described in plain words by the people who run it. Our team starts every company with a workflow workshop, where we map the work that costs you the most time and help your team describe the tool that replaces it. Most teams have their first real tool the same day.

A panel of top AI models plans each tool, a dedicated AI crew builds it, and every piece is checked for quality and security before it is saved. FORGE builds web, mobile and desktop apps, so the office works at a desk and the crew works from a phone in the same tool. Every app lives inside your company, people join only by invite, and owners, admins, builders and app users each see what their role allows. A complete record of who did what replaces the text thread as the history.

It is $49 a seat a month with 3 builds for the people who build, and the people who only use the apps are free, so the whole crew can be on the tool. Changes cost a small fraction of a build, packs of 10 builds are $150, and caps and alerts at 80 and 100 percent mean nothing bills by itself. See use cases, pricing, or talk to us.

Questions people ask

Sources

1. Asana: why work about work is bad
2. Zapier: repetitive tasks survey
3. Airtable plans
4. monday.com pricing
5. Power Apps pricing
6. AppSheet pricing