Frequently asked questions

Straight answers about Lawn-A-Matic.

Questions about payments, trials, modules, mobile use, data, and how the platform is built.

Does Lawn-A-Matic take a percentage of my customer payments?

No. Lawn-A-Matic is subscription software. Payment processing fees charged by the payment provider can still apply, but Lawn-A-Matic does not add a percentage of your payment revenue as its business model.

Is Lawn-A-Matic actually built by a lawn business owner?

Yes. It is built in Texas by an active lawn business owner and is shaped by daily field and office use.

Can I choose which modules my company uses?

Yes. Many specialized workflows are modular so companies can enable the tools they need. Availability can vary by plan and account configuration.

Does it support recurring lawn routes?

Yes. Recurring jobs, cascading reschedules, crew assignments, route planning, alternating service layers, and schedule controls are core operational workflows.

Can customers pay online?

Yes. Lawn-A-Matic supports online invoice-payment workflows and can also support saved payment methods, AutoPay, prepaid requirements, tips, and configured surcharges depending on the account setup.

Does it work on a phone?

Yes. The web platform is designed for responsive field use, and Lawn-A-Matic also has native iOS development alongside the web application.

How does public signup work?

Public signup is controlled by Lawn-A-Matic Super Admin and is off by default. When enabled, new companies complete spam protection, provide required company and owner information, consent to SMS account messages, and must verify both their email address and mobile phone before login is allowed.

Is there a trial?

New public accounts are configured for a 14-day trial once both activation channels are verified.

Can I see the software before signing up?

Yes. The public Gallery contains current screenshots from the production interface.

How do I report a bug or request a feature?

Customers can use Lawn-A-Matic support and bug-reporting workflows. The product is actively improved from real operational feedback.