01
The outcome is stated before the machinery
Opened the public AutoBounds product page.
The promise is concrete: turn manual delineation into an export-ready starting point from satellite imagery.
/
/
Webfield mapping
Evaluating a field-mapping workflow
/
Maya reaches the real app gate knowing the three-step workflow, available models, export formats, and credit model she is evaluating.
A live product-level walk for AutoBounds, framed around Maya Thornton's actual decision rather than a list of routes.
- 02
The workflow is point, process, export
Moved to the three-step workflow.
Maya can see what she must provide, what the model does, and what leaves the system before she evaluates implementation detail.
//
- 03
Models are compared by operating trade-offs
Opened the AI model comparison.
The model page makes speed, prompting, and boundary quality part of the product decision instead of presenting AI as one opaque button.
/ai-models/ai-models
- 04
Credits map to accepted work
Opened pricing.
Pricing explains that one credit buys one extraction and is deducted only when a result is accepted, which is the operational unit Maya needed.
/pricing/pricing
- 05
The real application starts at an account gate
Opened the production app demo route.
The walkthrough stops honestly at the production sign-in surface; projects, Labs, and exports remain blocked without an authenticated workspace.
/demo/demo
What this feature does
- Map and extract field boundaries
- Compare extraction models
- Organize projects, farms, and fields
- Export accepted boundaries
- Operate model and user settings