An estimate request form with photo uploads for landscapers
We build a web form where homeowners describe the job, upload photos of their yard, and send it to you. Each request is saved in one place and emailed to your office. It is a fixed-scope Tool build: $749, 5 business days, two rounds of tweaks.
The problem
Estimate requests often arrive as scattered texts, voicemails, and emails with a few blurry photos and no address. You end up calling back just to ask what the customer wants and where the property is. Photos get buried in message threads, so a quick look before a site visit takes longer than it should. A single form that asks the right questions and keeps the photos with the request cuts out most of that back and forth.
What we’d build
- A request form for name, phone, email, property address, service type, and a notes field
- A photo upload step where customers attach several yard photos from their phone
- A confirmation screen so customers know the request went through
- A saved list of requests with a detail view showing answers, photos, and a simple status (new, contacted, quoted)
- One email integration: each new request is sent to your office inbox with a link to the full details
A concrete example
A two-crew landscaping company wants to stop collecting requests by text. We build five screens: a request form, a photo upload step, a confirmation page, a staff list of requests, and a request detail page. The form asks for service type (mowing, cleanup, patio, planting, other), the address, and a short description. Customers upload photos from their phone. Each submission is saved and emailed to the office with a link to the detail page, where the owner changes the status as they follow up. The staff list is protected by one shared passcode. We deliver a hosted link and the full source code.
Pricing, Tool
This use case fits the Tool tier.
- Multi-step tool with saved data (quote builder, intake flow, tracker, simple dashboard)
- Up to 5 screens
- One integration (email, Google Sheets, Stripe, or a webhook)
- Hosted link + full source code
- Two rounds of tweaks
Need more? See all tiers.
Frequently asked
Can each crew member have their own login?
No. The Tool tier has no user accounts or roles. Staff get one shared passcode for the request list. Individual logins and roles are part of our Mini-app tier, which is a larger build with a different price and timeline.
Can it also send requests to our CRM or Google Sheets?
The Tool tier includes one integration, and here that is the email notification. Adding a second connection would go beyond this tier. If you need two integrations plus logins, the Mini-app tier is the better fit.
What happens after delivery, and what if we change our mind?
Hosting is included for 12 months, then $9.00 per month, or you can self-host with the source code. You get two rounds of tweaks. We refund in full if we decline the project before work starts. After delivery, there are no refunds.
Related use cases
- A shared chore chart for your family · We build a simple chore chart your whole household can open on any phone or tablet. Chores are saved
- A weekly meal planner that builds your grocery list · We build a small meal planner for your household. Pick meals for the week, and it combines the ingre
- A shared trip planner with an itinerary and a running tab · We build a small trip planner your group opens from one shared link. It holds the itinerary, tracks