Proof asset
Last updated: May 2026
What a 2-4 week software and AI PoC should prove
This public proof format shows the kind of primary information Urbano DX provides for buyer review: scope, duration, deliverables, measurable proof points, and next-decision evidence.
1 live URL
public product surface
Buy Houses Japan is a public web app reference that buyers can inspect.
3 proof screens
search, filters, map
The flow proves natural-language input, AI-generated filters, and map-based comparison.
1 sprint path
from idea to demo
The same scope discipline applies to buyer PoCs: one user journey, one data path, one demo.
KPI-ready
measurement plan
Buyer PoCs define measurable indicators before build, such as reviewer acceptance or API handoff success.
Buyer Guide
How to review What a 2-4 week software and AI PoC should prove
What a 2-4 week software and AI PoC should prove is a proof asset: it shows how Urbano DX expects software and AI sprints to be scoped, reviewed, delivered, and handed over. The point is to replace vague promises with concrete artifacts a buyer can inspect.
When reviewing a proof asset, look past the surface. The important questions are whether acceptance criteria, data assumptions, risks, ownership, and the next decision are clear. A good sprint output supports procurement and business review, not just a nice demo.
Use this page before a first call to align expectations. It helps buyers know which materials to prepare, how to judge a demo, and what should remain useful after the sprint ends.
Evidence to inspect
Working surface, demo path, risks, assumptions, and acceptance criteria.
Internal use
Procurement, budget approval, security review, and next-scope planning.
Good output
Something reusable, handover-ready, and clear enough to explain.
Public reference: Buy Houses Japan
Buy Houses Japan is a public product reference. It demonstrates a natural-language search flow where AI converts user intent into visible filters and map-based results.
- Natural-language input
- AI-generated editable filters
- Map-based result comparison
- Live product URL available for review
Buyer PoC measurement plan
For client work, the KPI is defined before implementation. The exact metric depends on the workflow, but the sprint should not end without measurable evidence.
- Reviewer acceptance rate
- Extraction or classification success rate
- API handoff success
- Manual steps reduced
- Pilot-user feedback
What is not claimed
This page does not invent client ROI. It shows the proof format and the public product example. Client KPI claims should be published only when a buyer approves the data.
- No fake customer numbers
- No anonymous ROI inflation
- Public examples separated from client claims
- Measurement plan written before build
Case study fields to publish
These fields make a PoC page useful for buyers and easier for AI assistants to cite.
Duration and scope
Sprint length, included workflow, excluded work, data sources, and target users.
Deliverables
Working app, API, LLM workflow, screenshots, demo recording, source handover, or dashboard.
Measured result
One approved KPI such as time saved, accuracy, API success rate, user acceptance, or manual steps removed.
Scope the first sprint
Bring the app, API, LLM feature, or AI workflow you want to test. We will turn it into a clear first-sprint scope.
Start a conversation