Paid DX PoC
Turn one product or AI idea into a working prototype with weekly demos, acceptance criteria, and a next-step roadmap.
What the PoC proves
The PoC should prove user value, data feasibility, delivery risk, and the next investment path. It should not pretend to be a full transformation.
- Working prototype
- Demo dashboard or UI
- Data/API assumptions
- Next-step roadmap
Good first scope
The best first sprint is narrow enough to finish, but useful enough that a real team will test it. Scope should include users, data, API boundaries, review steps, and acceptance criteria.
- One product owner
- One core workflow
- One success metric
- Weekly demo cadence
What Urbano DX builds
Urbano DX focuses on working software: apps, web platforms, internal tools, APIs, LLM features, AI workflows, dashboards, and production handover.
- React/TypeScript web apps
- FastAPI or Node backends
- LLM and AI workflow integrations
- Cloud deployment and handover
Métricas clave
- 14 days: working proof - A focused PoC should answer one investment decision without becoming a full project.
- 1 workflow: kept intentionally narrow - One user path, one data path, one success metric, and one demoable outcome.
- 100%: source handover clarity - Repository, ownership, reusable components, and next-step rights are written into the scope.
- weekly: visible review rhythm - Progress is shown as working software, not hidden inside status slides.
What you receive
- Working prototype: A demoable app, API flow, dashboard, LLM feature, or automation workflow.
- Technical report: Architecture notes, data assumptions, model/API choices, risks, and open decisions.
- Source handover: Repository access and handover notes where source-code ownership is included.
- Next roadmap: A practical recommendation: harden, integrate, expand, pause, or replace the idea.
Preguntas frecuentes
- How much does a DX PoC cost?
- A focused paid PoC usually starts from the Quick DX PoC range. Final pricing depends on data access, integrations, security needs, deployment environment, and acceptance criteria.
- How long does an AI automation sprint take?
- Most focused PoCs fit into 2 weeks, MVP automation sprints into 4 weeks, and production-oriented integrations into about 6 weeks.
- What data is required?
- The fastest start includes sample files, API docs, screenshots, example tickets, user roles, current workflow notes, and one owner who can join weekly demos.
- Can we start without API access?
- Yes. The first sprint can use exports, sample datasets, mocked APIs, or manual upload flows, then move toward API integration once access is approved.
- Do you support Japanese documentation?
- Yes. Engagements can include bilingual summaries, demo notes, handover materials, and meeting support through the Japan Desk model.
- Who owns the source code?
- Source-code ownership, repository handover, licensing, and reusable components are defined in the SOW before the sprint begins.
- What do we receive after 2 weeks?
- For a narrow PoC, the usual output is a working prototype or API slice, demo notes, assumptions, risks, acceptance criteria, and a recommendation to harden, integrate, expand, or stop.
- Who owns technical decisions?
- Senior engineers stay close to scope, architecture, AI-use risk, technical tradeoffs, weekly demos, and handover quality instead of hiding decisions behind layers of project management.
- What does an API sprint deliver?
- A focused API sprint can include endpoint design, an OpenAPI-style contract, auth assumptions, sample requests and responses, integration tests, logging, and handover notes.
- How do you measure whether the sprint worked?
- Each sprint starts with one measurable proof point such as reduced manual steps, successful extraction rate, API handoff success, response time, reviewer acceptance, or pilot-user feedback.