Proposal for review · Revised 6 October 2026
Quality Scanner
for Pennrose Farms
Start with one or two inspectors using the web app. Build the iPad app, bell-pepper model and coverage view around what the first inspections teach us.
Eight-week delivery target · Fixed project price: $12,300.
First-use target: week 2, with week 3 as a buffer.
Prepared for Lisandro Duenas · Scope and milestone fees for review
Existing foundation
The inspection flow is already available.
From photos to a signed report
Create a sheet, add sample and supporting photographs, request suggestions, correct counts and defects, submit, and browse the report and its PDF.
A deployed web app
Sammy received access and confirmed he could sign in. The first inspectors still need their facility, permissions and reporting workflow checked on the devices they will use.
Finish operational readiness
Protect stored photos, verify backups and recovery, apply usage and upload limits, and ensure reports with many photographs generate reliably.
Extend the working system
The native iPad workflow, a Pennrose-trained defect model and the incoming-product coverage comparison each need a defined first release.
The first milestone verifies and prepares the existing flow for real use. Inspectors confirm every report; interim AI suggestions remain editable.
Milestone 1 · First inspectors using the web app
Complete the work needed for first use.
Fixed fee: $2,400 · Native iOS is not required.
Use the existing inspection flow
- Start a sheet and add sample photographs.
- Review suggestions and correct counts or defects.
- Save, submit and retrieve the report and PDF.
- Configure the first facility and inspector accounts.
Complete and verify readiness
- Move new inspection photos into private storage.
- Set up backups and verify recovery of records and photos.
- Apply usage limits and handle oversized uploads.
- Generate photo-heavy PDFs reliably and test the full flow on the pilot device.
Define: the first facility and users, required PDF/email output, and the reporting checks for first use. First use can start sooner if readiness checks pass.
Milestone 1 · Delivery sequence
Start the pilot in the first two to three weeks.
Finish and verify readiness
Complete the storage, backup, upload-limit and PDF work. Configure the first facility and accounts, and run the complete inspection flow on the intended device.
Start the first inspector
Begin real inspections once the readiness checks pass. Observe the first reports, compare them with the current process and capture corrections and defect photographs.
Resolve initial issues
Use this time if readiness work needs longer. Otherwise, correct issues found during use and add a second inspector when the first workflow is reliable.
Weeks run from an agreed start date. The eight-week target assumes timely feedback and inputs. If first use moves into the third-week buffer, review the later dates. Photo collection starts with the pilot.
Milestone 2 · A focused iOS release
Take the validated inspection flow onto the iPad.
Fixed fee: $4,950 · Reuse the existing Flutter foundation
First-release scope to review
- Sign in and choose the assigned facility.
- Start a sheet and capture sample photographs.
- Review suggestions and correct labels or counts.
- Save, submit, open reports and share their PDFs.
Keep the release focused
- Verify the flow on the pilot iPad and distribute a test build.
- Agree how drafts and interrupted uploads recover.
- Defer manager/admin tools and a separate photo-gallery experience unless essential.
- Scope full offline operation separately.
Define: which web functions must be in the first native release, the minimum connection-recovery behavior and the device distribution route. Device distribution may add external waiting time.
Milestone 3 · Bell-pepper AI
Collect examples early. Train a bounded first version.
Fixed fee: $3,300 · Collection starts with the web pilot.
Prepare and evaluate a first model
- Agree the bell-pepper defect labels and photo requirements.
- Use inspector-confirmed examples and reserve a separate evaluation set.
- Train and evaluate a first model version using the agreed dataset.
- Compare its counts and defect labels with confirmed inspection results.
Release according to measured results
- Agree the release criteria before training.
- Integrate a version that meets those criteria.
- Keep inspector correction and a usable fallback.
- Review further training rounds and other commodities separately.
Define: the first defect set, available photos and evaluation criteria. Training requires usable labelled examples; missing data may shift the dates. Inspector corrections are collected for reviewed training rounds; the model does not retrain after every inspection.
Milestone 4 · Inspection coverage
Start with a simple inspected-versus-missing view.
Fixed fee: $1,650 · Validate against Sammy’s examples.
Include the first useful comparison
- Import one agreed incoming-product CSV or Excel format.
- Match products or lots to recorded inspections.
- Show inspected, missing and unmatched items.
- Open the associated report and quality result.
Keep later analysis separate
- Agree how partial inspections and duplicates count.
- Validate the comparison against Sammy’s Excel examples.
- Defer additional file formats and direct ERP integrations.
- Review broader trends and predictive risk analysis after the basic comparison works.
Define: the first input file, matching identifiers, the meaning of “inspected” and the comparison examples. This milestone can move earlier if it is more useful than iOS or model training.
Fixed milestone prices
Four milestones. A $12,300 project.
| Milestone | Delivery target | Fixed fee |
|---|---|---|
| 1. First web users | Weeks 1–2 | $2,400 |
| 2. Focused iOS release | Weeks 3–5 | $4,950 |
| 3. First bell-pepper model evaluation | Weeks 6–7 | $3,300 |
| 4. Basic coverage view | Week 8 | $1,650 |
| Total project | 8 weeks | $12,300 |
First web use targets week 2, with week 3 as a buffer. Later dates depend on timely review, labelled photos, sample files and device distribution; agree any schedule adjustment as it arises.
Review each milestone against its stated completion criteria. Scope changes and additional model-training rounds are priced separately before work begins. Hosting, support and production AI/compute are separate from the project fee.
Hosting and support
Size the service for the first group of users.
Define a practical service allowance
- Hosting and private photo storage.
- Backups and recovery checks.
- Routine maintenance and a bounded support allowance.
- Review capacity as inspectors and inspection volume grow.
Price variable costs separately
- Production AI usage and model-training compute. Development AI tools are included in the milestone fees.
- Additional training and substantial feature changes.
- Support beyond the agreed allowance.
- Devices and app distribution-account fees.
Storage starts with the first inspection. Pennrose’s facility and inspector counts, devices and roles will guide later capacity and rollout planning.
Decisions for the next revision
Define what belongs in each first release.
| Decision | What to settle |
|---|---|
| First web users | Which facility and 1–2 inspectors start? Which reports, email outputs and permissions are essential? |
| Start and review process | When does work start, who reviews each milestone, and what evidence establishes completion? |
| iOS first release | Which functions must move to the iPad first, and which can stay in the web app? |
| Bell-pepper model | Which defects and examples are ready? Which confirmed examples and evaluation criteria will guide the first model version? |
| Coverage view | Which incoming-product file and identifiers will we use? What counts as an inspection? |
| Next priority | After first use, should iOS, the model or coverage come next? How much onboarding and support is needed? |
Sammy’s response on facilities, inspectors, devices, roles and phased rollout remains pending. The four milestone fees total $12,300. Review the scope, acceptance checks and dates with Lisandro; further expansion is agreed separately.