FarmsFlo training

Updated October 17, 2026. Use this guide to qualify a farm, demonstrate a useful recordkeeping workflow, explain current plans, and share the correct affiliate link.

What FarmsFlo helps a customer accomplish

FarmsFlo brings crop planning, fields, inventory, harvest records, and related farm operations into a browser application. Paid plans extend that work into livestock/feed, employees, tools, sales, and customer records. The useful promise is organized information that people can maintain and retrieve. It is not a guarantee of increased yields, profitability, tax compliance, or fewer crop losses.

A good first prospect is an owner or manager of a small working farm, market garden, or expanding homestead who has information scattered across notebooks and spreadsheets. A farm with several people entering work may need the paid team features. A solo grower can try the Free plan on a limited real growing project.

Check scope before recommending. Someone who wants only breeding dates and animal records may fit the separate HerdFlo product better. Someone needing a particular machinery integration, accounting package connection, audited payroll service, guaranteed offline operation, or enterprise agronomy platform needs an explicit capability check. Do not claim those requirements are covered because FarmsFlo has a broad set of tabs.

Ask useful discovery questions

Begin with the work, not subscription price:

• How do you track what was planted, where, and when?
• How do you know what seed and supply stock remains?
• Who enters harvest quantities and employee hours?
• How many fields, active crop records, inventory items, and people need access?
• Are sales/customer records part of the immediate need?
• Which one repeated mistake or missing record would you like to fix first?
• Will the people doing the work have an internet connection?

Choose one small demonstration from the answers. For a market grower, follow one crop from a field and seed inventory into a harvest. For a crew manager, start with who needs access and a timesheet. Avoid presenting every feature as equally important.

Current plans and important price differences

The current web pricing page shows:

Paid web offers include a 14-day trial through card checkout. The selected subscription renews automatically after the trial unless canceled. Have the customer read the actual checkout’s card requirement, trial eligibility, amount, renewal date, and cancellation terms. Free is advertised as no card and free forever. Do not promise that every trial route behaves like the Free signup or that trial eligibility repeats indefinitely.

The pricing comparison mentions an AI option at an additional $5/month on Pro, while the prominent AI offer points to Complete. If a customer specifically wants the standalone add-on, verify that option in their current billing screen or ask support before promising it. Complete explicitly includes AI. Never buy a more expensive plan on the customer’s behalf to resolve unclear copy.

Some account screens can use an older internal plan label such as Basic or Enterprise. Compare actual entitlements and the checkout amount to the current named offer; an unfamiliar badge alone does not establish that the customer has the wrong subscription.

Recommend the smallest plan that covers the immediate use. One grower with two fields and eight crops may start Free. A farm needing sales/customer tracking and ten employees can consider Pro. Financial reports/tax forms and included AI are reasons to examine Complete, not proof that everyone needs it.

Lesson 1 — Create the farm account

Ask the customer to open your current personal FarmsFlo link from the Residual Apps dashboard before registering. The landing page provides Get Started, View Plans, and Sign In. Returning users should sign in to their existing farm instead of creating a duplicate organization.

The customer enters their own account and farm information. Do not ask for their password or payment card. When the setup wizard appears, review its farm location and growing-zone information. The first step asks for farm name, city, state, and ZIP code. Subsequent setup covers USDA zone and frost dates, with greenhouse/indoor-start context in the farm location settings.

Location and frost information affect suggestions. Correct it rather than accepting a guessed zone. A frost date or AI planting recommendation is planning assistance, not a weather forecast or guarantee. Save the setup, then check the farm name at the top of the dashboard so you know which organization you are using.

Start with one genuine workflow. Importing an entire season before learning how records connect can create avoidable cleanup.

Lesson 2 — Know the navigation and permissions

The dashboard has a horizontally scrollable navigation row. On a small screen, scroll it sideways to locate additional tabs. Depending on access, the current interface includes Dashboard, Employees, Timesheets, Inventory, Crops, Livestock, Harvests, Fields, Tools, Products, Sales, Customers, and Reports, with administrative financial/settings options where permitted.

A missing tab may reflect role permissions. An upgrade message may reflect plan entitlement. These are different causes. An employee should ask the farm administrator for appropriate access rather than registering another farm or sharing an owner’s password.

For a first demonstration, concentrate on Fields, Inventory, Crops, and Harvests. Explain that a crop record describes what is being grown; a field describes its location; inventory represents supplies; and a harvest records output. Treating these as interchangeable makes later reporting harder to interpret.

Lesson 3 — Define a field

Open Fields and choose Add Field. Enter a clear Field Name, then the available size and unit. Units include acres, square feet, square meters, hectares, beds, and rows. A number without the right unit is misleading, so confirm both.

The form also offers soil type, irrigation, status, and notes. Use what is known; optional fields are not an invitation to guess. The status choices include Active, Fallow, Preparing, and Inactive. Use Save Field, then find the saved field again.

For a demo, “Demo North Bed” with ten beds is clearly fictional. Never mark a real production field inactive just to show a control. Free includes three fields; reaching a limit is a plan conversation, not a reason to combine unrelated fields under an inaccurate name.

Lesson 4 — Add inventory and connect a crop

Open Inventory and use the add-item workflow. Select the actual item category, name, quantity, and unit offered by the form. Keep units consistent with how the farm purchases and uses the item. Seeds and other supplies have different purposes; do not record a supply purchase as a harvested product.

Open Crops → Add Crop. The form includes Crop Name, variety, planting date, expected harvest, earliest/latest planting dates, planting strategy, status, quantity planted, field/location, and notes. Select the saved field and record accurate dates. Available status choices include Planned, Planted, Growing, Harvested, and Failed.

Where a seed inventory item is linked, the form offers Seed Quantity Used. Review that amount before choosing Save Crop. The current interface explicitly says seed inventory is deducted when creating a new crop. Editing an existing crop does not automatically perform another deduction. Later usage adjustments belong in Inventory → Use.

This distinction is a useful part of your demonstration: enter the crop once, then inspect the crop and related inventory. Do not repeatedly create the same crop when a screen is slow; first check whether the original record saved.

Optional AI planting suggestions require the relevant entitlement. Treat suggestions as information to review against actual location, growing conditions, and agricultural guidance. Do not advertise AI plant diagnosis as a definitive disease identification service.

Lesson 5 — Record a harvest

Open Harvests and the Record Harvest form. Choose the correct crop, the actual harvest date, quantity, and unit. Optional details include quality grade and notes. Select Save Harvest, then review the saved entry.

The form describes an automatically calculated seed-cost-per-harvested-unit figure and a manual cost override. That calculation depends on the entered seed costs and harvest quantities. It is not a complete business profit calculation unless the underlying records and accounting treatment support that interpretation. Do not enter a made-up override to make a demonstration look profitable.

Batch Harvest lets the user enter quantities for multiple crops on a common date, leaving other crops blank. Demonstrate it only when that matches the actual work. A waste workflow reduces the usable recorded harvest; it should represent real loss, not an easy way to delete an accidental quantity.

A good daily habit is to record the harvest while the quantity and unit are still clear. End the demo by finding the same entry again so the customer sees the complete save-and-retrieve cycle.

Lesson 6 — Team, tools, sales, and reports

Paid farms can extend the basic growing workflow. Employees and Timesheets organize people and recorded work. Give each person the intended access and verify the farm context. A time record does not itself prove payroll was paid, taxes filed, or labor rules satisfied.

Tools supports equipment-related organization and checkout/maintenance workflows. Livestock introduces animal/feed work under eligible plans. Explain the specific screen the customer needs; do not imply that a FarmsFlo purchase also unlocks a separate HerdFlo subscription.

Products, Customers, and Sales support recording what is sold and to whom. Entering a sale is not necessarily processing a payment or depositing money. Inspect the actual invoice/payment status before saying a customer has paid. Similarly, a report reflects what was entered, including missing or inconsistent units and dates.

Complete includes financial reports and tax-form tools. Describe them as recordkeeping/export assistance. An affiliate should not decide deductions, employee classification, or tax filing requirements. The customer should review outputs with their own qualified adviser before relying on them.

Use the AI assistant only when enabled on the actual account. Review its response before acting. Keep sensitive customer, employee, and tax information out of demonstration chats.

Lesson 7 — Billing and troubleshooting

The farm administrator handles plan selection and billing. Use the account’s billing management control for a web subscription and read the hosted billing screen before confirming changes. Canceling renewals and deleting farm data are different actions. Do not use deletion, a second subscription, or a second organization as a billing repair.

“I cannot find the tab.” Scroll the navigation on mobile, then check role permissions and plan access with the farm administrator.

“My crop did not save.” Read the error, confirm required fields and connection, and look for the record before resubmitting. Capture the exact wording for support.

“Seed inventory changed unexpectedly.” Check whether the crop was newly created with a linked seed quantity, whether units agree, and whether a separate Inventory usage entry was also made.

“I need this entirely offline.” This guide does not establish full offline support. Demonstrate the real browser workflow on a connection and verify the requirement before purchase.

“The AI option costs something different.” Read the actual offer and ask support to reconcile the current add-on route. Do not promise a checkout that has not been shown.

“Does it replace my accountant or agronomist?” No. It organizes information and provides tools; qualified people still make professional decisions.

For product help, use the support/contact route shown in the account or current official site. If you cannot locate it, support@residualapps.com can help route a product inquiry. Include the farm/account email, tab, device/browser, exact steps, error, and expected result. Do not send passwords, card details, or employee tax documents.

A focused demonstration and sales conversation

Use a demo farm with fictional “Demo North Bed,” “Demo Salad Mix,” and a synthetic harvest. Prepare it before the conversation; do not alter a working farm or invite real employees just to fill a screen.

1. Ask which record causes the most repeated trouble.
2. Show the farm identity and Fields navigation.
3. Create or open the demo field and explain the size unit.
4. Show one crop, its location, and its seed-inventory relationship.
5. Record a small fictional harvest and retrieve it.
6. Match user/field/crop counts and required features to the current plan.
7. Offer the customer a first task: add one real field and one crop through their own account.

Introduction: “How do you connect your planting notes with inventory and harvest quantities? FarmsFlo puts those records in one place. We can start with one field and one crop. I’m an affiliate and may earn a commission if you purchase through my link.”

When someone says their spreadsheet works, ask whether shared entry, linked inventory, or finding a crop’s history is actually a problem. If it is not, do not force a change. After an invited demonstration, a useful follow-up is: “Did your first crop save under the correct field, and are the inventory units right?”

Your referral and payout workflow

The current Residual Apps catalog publishes $10–$25 per month per qualifying paid FarmsFlo plan. Use the dashboard’s current plan-specific terms for an exact reward; do not assign an unverified rate to an add-on or quote an annual reward the catalog does not establish. A Free account and an unpaid trial are not paid commissions.

Copy your own current FarmsFlo share link or QR from Residual Apps and check its destination. Let the new customer open it before signup, preferably in the same browser. A generic homepage link, crop barcode, inventory QR, or another partner’s link is not your affiliate tracking link.

Explain that attribution can be affected by existing accounts, browser storage, device changes, and checkout paths. Monitor clicks and paid activity separately. Published reward figures are subject to qualifying payment, eligibility, refunds, cancellations, and program terms; they are not take-home income guarantees. Disclose the affiliate relationship near the recommendation.

The quoted rewards are gross commissions. Under current standard terms, Residual Apps keeps 20% of commissions earned, capped at $9.99/month. Review the partner-program training for payout timing, eligibility, and the shared program process.

Practice and readiness answers

Before promoting, practice the field → crop → harvest workflow in a demo farm and identify where plan and role restrictions appear.

1. One user, two fields, eight crops, twenty inventory items? Free fits those stated limits.
2. Sales/customer tracking and twelve employees? Pro is the first advertised fit.
3. Financial reports, tax forms, and included AI? Review Complete.
4. Does editing a crop automatically deduct seed again? No; the form says deduction happens at creation, with later usage through Inventory.
5. A harvest quantity looks wrong: first check? Crop, date, quantity, and unit.
6. A crop barcode is the affiliate QR? No; use the personal Residual Apps product link/QR.
7. Free signup means commission? No; qualifying paid activity is required.
8. Can you guarantee AI diagnosis or increased profit? No.

Use the app and help us improve it

Use the app yourself before recommending it. Complete one useful workflow in your own account or an authorized demo, then find the saved result again. A paid subscription is not required to become a partner; use the free option or an available preview and be clear about what you have actually tried.

If you use this app, tell us what works, where you get stuck, bugs you can reproduce, and what you wish it did next in Partner Care. Include the app, web/iOS/Android, installed version or browser version, steps, expected result, and what happened. Say whether it affects your own use or a demonstration. Please report unclear training or a screen that differs from this guide too.

Keep customer names, email addresses, medical records, payment details, passwords, and sign-in codes out of feedback. Use fictional examples and remove private information from screenshots. Urgent account or billing problems still belong with the product support route above.