Illustrative example · Landscaper
How a landscaper could take crypto for recurring service
An illustrative walk-through of a route-based service business with recurring clients, where monthly billing and on-site collection shape the approach.
This is a composed educational scenario built to show how the pieces fit for this kind of business. It does not describe a real CryptoLic customer, and it promises no particular result. Any figures are illustrative. We do this instead of testimonials so nothing here can be mistaken for a real endorsement.
Picture a landscaping business running a weekly route of recurring clients, plus one-off projects like a new install. Recurring clients are billed monthly; projects are invoiced on completion. Collection often happens in the field.
This example follows how such a business might add crypto for both patterns. An honest note: recurring crypto auto-billing is still immature, so this uses monthly requests. Figures are illustrative.
At a glance
| Business | Landscaper, recurring route plus projects |
|---|---|
| Typical ticket | $120 monthly to $4,000 project (illustrative) |
| Current methods | Card, check, bank transfer |
| Goal | Simple recurring billing and lower project fees |
| Equipment added | None; a phone app |
How they take payment today
Recurring clients pay by card or check monthly; projects by transfer or card. Chasing monthly payments takes time, and card fees on a big install are significant.
The pain points that started the question
- Time spent chasing monthly recurring payments.
- Card fees on larger project invoices.
- Collection that often happens on site, from a phone.
Why crypto came up
A low-fee payment collected from a phone suits field work, and a monthly payment request is simple to send to a recurring client. On big installs, the crypto fee comes in below cards.
The initial concerns
- "Auto-billing for the route?" Not automatic yet, so a monthly request per client.
- "Which rail?" On-chain for projects, Lightning fine for a monthly service charge.
- "Hold or convert?" Auto-conversion to dollars for clean books.
How they researched it
The owner read the music-teacher example for the recurring-billing reality, the HVAC example for field collection, and the Payment Solutions Center for a phone-friendly, dollar-settling processor.
The decisions they landed on
- Method: Lightning for monthly charges, on-chain for projects.
- Custody: a processor with dollar settlement.
- Recurring: a monthly payment request per client, not auto-billing.
- Collection: a phone QR or link for on-site project payment.
The implementation, step by step
- Chose a phone-friendly processor with dollar settlement.
- Set a monthly request routine for recurring clients.
- Added a crypto option to project invoices.
- Offered it to clients who preferred it, keeping other methods.
Equipment and costs
No hardware. The cost was the conversion fee, favorable against card fees on projects. Illustrative and service-dependent.
Lessons worth keeping
- Monthly requests worked where crypto auto-billing does not yet.
- Phone collection fit route-based field work.
- One setup covered recurring charges and one-off projects.
Common misconceptions and pitfalls
- Misconception: crypto can auto-bill a recurring route. That is still immature.
- Pitfall: on-chain for a small monthly charge where Lightning is cheaper.
- Pitfall: forcing it on clients happy with their current method.
Recommended next steps for a similar business
- Take the readiness quiz with recurring and project work in mind.
- Read the music-teacher and HVAC examples.
- Pick a phone-friendly, dollar-settling processor.
- Set a simple monthly request routine.
The CryptoLic resources used in this example
- Merchant Readiness Quiz
- Music teacher educational example
- HVAC company educational example
- Payment Solutions Center
Every business is different. The best next step is to take the readiness quiz and get a plan matched to your own numbers, then dig into the resources above.
More examples