ForwardThis

13 October 2026 · By Sam Thomas

How to Choose Among Make Alternatives

Compare Make alternatives by workflow fit, ease of use, cost and data handling, then test a small job before you switch or add another approach.

Looking for workflow automation alternatives? Start with the job that’s causing friction, not a long list of features. A good replacement should fit how work reaches your team, what must happen next, and how much control you need over each step.

Use these five steps to set clear requirements, check costs and data handling, then test a small example. You may find that a different platform fits, or that ForwardThis is better for one-off admin that starts with an email.

Table of Contents

Step 1: Pinpoint What Is Not Working

Write down the exact problem before you look at other options. “The platform is too complicated” is a feeling, not a requirement. Try to name what goes wrong: a scenario is hard to maintain, a task starts from email, usage is hard to forecast, or the team lacks time to build and fix flows.

Look at a few recent jobs and mark where each one starts. Does a new record arrive in an app and need the same steps every time? Does a person need to read an email and decide what should happen? Those are different jobs. A scheduled process suits a different approach from a one-off request with changing details.

Then separate the main issue from the side effects. If a flow fails because a field changed, the fix may be better error handling. If staff keep copying client requests from email into a CRM, the deeper issue may be the handoff, not the flow builder. For an overview of the system types involved, see this guide to workflow automation software.

Check your current usage too. Review how your provider calculates charges, and whether each module action or scenario run affects the bill. Costs can vary with the number and type of actions in a run. Count the actions in a typical run and check your actual usage before deciding that a different plan would be cheaper.

Keep the evidence simple: list the task, how often it occurs, who checks it, and what goes wrong. That gives you a useful test case later.

Step 2: Map the Work the Replacement Must Handle

Describe the work as it happens today, from the first signal to the final check. Write down what starts it, which data moves, what decision points exist, and who needs to approve the result. Note any exceptions that occur often, such as a missing email address or a client request that needs a human reply.

For a repeating task, sketch the sequence in plain words. For example: when a new form response arrives, create a record, assign an owner, then send a notice. Mark any branch where the next action changes based on a field. This helps you see whether you need a visual builder, a code-based approach, or only a way to handle requests one at a time.

For each workflow builder you consider, review its integration directory to check which apps and actions it supports. Look at how data passes between steps and how fields are mapped from one step to the next. Don’t count an app as a match until you’ve checked that the specific action your process needs is available, not just the app’s name.

Now note what must stay manual. A person may need to review a client message before it goes out, or confirm a record before many items change. These checks aren’t wasted steps. They’re part of the process and should appear in your requirements. If most requests arrive as messages, ForwardThis and other tools for email-driven admin may be worth assessing alongside workflow builders.

Keep the map to one page. If you can’t explain the process simply, it will be hard to test a replacement fairly.

Step 3: Score Candidates Against Usable Requirements

Turn your map into a short scorecard. Rate each option against the same needs, using “meets,” “partly meets,” or “doesn’t meet.” Add a note beside each rating that says what you tested. This keeps a polished demo from outweighing a missing action your team needs every day.

  • Workflow fit: Can it start from the event you use? Can it handle the needed branches or approval pauses?
  • App coverage: Does it support the exact records and actions in your map?
  • Ease of upkeep: Can the person who owns the process understand a failed run and make a safe change?
  • Technical control: Does your team need code, custom API calls, or self-hosting, meaning the software runs on infrastructure you manage?
  • Visibility: Can you see what ran, what failed, and what needs a person to step in?

Weight the criteria by risk. If a missed sales lead costs more than a few minutes of setup, app coverage and failure alerts should count more than a neat canvas. If only a technical team can maintain the system, include their time in the score.

Think about who’ll use it on a busy day. A process owner may want a clear visual path. A developer may want access to code and APIs. A small team may prefer fewer setup steps, even if that means less control. There isn’t one right balance for every job.

For work involving AI, test the task that uses it rather than relying on a feature label. Check what information it reads, what output it creates, and where a person reviews that output. A guide to AI for email-led admin can help you frame those checks.

Finally, give each score a confidence mark. If a claim comes only from a demo, mark it for a pilot. If you’ve tested the exact action with sample data, you have stronger evidence.

Step 4: Check Total Cost, Limits and Data Handling

Compare the full cost of running the process, not just the entry plan. List the subscription, expected usage, any extra charges, and the staff time needed to set up and maintain the system. Include the cost of a failed run if someone must spot it and repair the data by hand.

Use one typical month as your first estimate. Count how often the process runs, then count every action inside each run. Some credit-based automation plans charge credits for individual actions, with advanced features sometimes using more. Allowances can also depend on how many credits you buy, so a multi-step process may use far more credits than its run count suggests.

Don’t assume that the lowest starting price is the lowest total cost. A tool with less setup may save staff time, while a self-hosted option may bring infrastructure and upkeep work. Ask who handles updates, access controls, backups, and failure checks. Record those responsibilities beside the price.

Next, check how the system handles business data. Ask what it stores, for how long, who can access it, and whether you can remove or export it when you leave. If the process touches customer details or financial records, involve the person who owns your company’s data rules before connecting an account.

For email-based jobs, be precise about mailbox access. ForwardThis only acts on email sent by a verified address. It doesn’t watch the inbox in the background. When a task asks it to use a connected mailbox, it can search, read, draft, label, or send within that request. Email content is kept briefly to support undo, then deleted; an action record is kept for 90 days.

ForwardThis charges by email action rather than by each action inside a multi-step job. The Free plan includes 10 actions a month. Starter has 100 for $15 a month, while Pro has 400 for $39 a month. One email counts as one action, even if several app updates follow. Compare that model only for work that starts with an email and fits its supported actions.

Paper-cut diagram showing workflow costs, usage limits and data handling checks.

Email management options are a separate category from systems that run scheduled app-to-app processes. Keep that distinction in your cost sheet so you don’t compare unlike jobs.

Key Takeaway: Price the work you’ll run, then add the time and care needed to keep it safe.

Step 5: Run a Small Pilot and Choose the Right Fit

Test one useful process before moving a whole team. Pick a task that happens often enough to learn from, but isn’t risky if you need to stop and fix it. Use sample records or a small set of low-impact data first.

Write down what success looks like before the test. For example, the right record appears in the right place, the key fields match the source, and the process leaves a clear record of its actions. Add a failure test too, such as a missing field or an unavailable app. You need to know what happens when the easy path breaks.

Run the same test more than once. Check the result yourself, then ask the person who will own the process to repeat it. If a developer built the flow, a non-technical colleague should still be able to tell whether it worked and who to ask for help.

For a one-off email request, ForwardThis works differently from a visual builder. You forward or write an email to do@forwardthis.io with a plain-English instruction, such as “Add this person to HubSpot and remind me Friday.” It carries out the supported work in connected apps and replies with a record of what it did. You don’t build a workflow first.

That approach has clear limits. It isn’t an inbox organiser or an autoresponder. Actions that reach another person, are hard to reverse, or affect many records wait for approval; most actions can be undone for 24 hours.

Keep the process that needs fixed, repeatable steps in a system built for that job. Use ForwardThis only where an email starts admin that changes from request to request. A small pilot will show whether that line fits your work.

Pro Tip: Keep a copy of the original request and compare it with the final app records before you approve the pilot.

Frequently Asked Questions

How do I choose an automation alternative?

Choose by matching the replacement to the work that fails or takes too long today. Write down the starting event, app actions, decision points, approval needs, and monthly usage. Then score options against those needs and test one low-risk process. A tool that fits your workflow matters more than a long list of features.

What should I check before switching automation platforms?

Check that the replacement supports each app action your process uses, along with its branches and error handling. Estimate the cost using actions inside a run, not only the number of runs. Also review data access, retention, export, and who will maintain the setup. Test a representative process before you move important work.

Can ForwardThis replace a workflow automation platform?

ForwardThis can handle some email-led admin, but it isn’t a general replacement for a workflow automation platform. It acts only when you send it an email and doesn’t run scheduled or recurring jobs. It fits requests that start in email and need supported actions in connected apps. Keep a workflow builder for processes that must run on their own.

How much does ForwardThis cost?

ForwardThis has a Free plan with 10 actions a month, Starter with 100 for $15 a month, and Pro with 400 for $39 a month. One email is one action, regardless of how many replies, approvals, or undos follow. You can buy 100 extra actions for $10, and those purchased actions don’t expire.

Conclusion

Choose based on the process you need to fix, then run a small test before moving more work. If the task begins with a changing email request, try it with ForwardThis; if it needs to run on a fixed schedule, keep looking for a system built for that pattern.