Scope and acceptance criteria
Define the workload, services, test evidence and decision owner before implementation.
AWS PoC in Vietnam and global markets
Start an AWS PoC with TitanBases
A proof of concept should answer a specific business and technical question. Share the workload, the AWS account that will run it and what a successful result looks like. TitanBases helps define the scope, review relevant AWS programs and agree on next steps.
What to prepare for an AWS PoC
You do not need a finished architecture diagram to begin. Share the 12-digit AWS Account ID and root email as identifiers; never send passwords, access keys or MFA codes. Describe the use case, workload and intended production direction; current or proposed AWS services, integrations, data and security constraints; measurable success criteria, test window and decision owner; and an approximate monthly AWS usage estimate if available. TitanBases can help refine a preliminary design and acceptance criteria before implementation.
A defined path from request to PoC decision
The first conversation turns a rough idea into a workload, evidence and decision path. Each step has a distinct purpose.
Program fit, not assumed credits
Review relevant AWS programs and required evidence. Eligibility and approval depend on AWS and the program.
AWS technical discussion when appropriate
For workloads estimated at USD 5,000+ in monthly AWS usage, TitanBases can coordinate with an AWS AM and SA, subject to scope and availability.
Recorded PoC outcome
Test against agreed criteria, capture actual usage and decide whether to revise, stop or plan production.
How an AWS PoC request moves forward
The sequence applies to scoping work in Vietnam and international markets. Program availability, AWS involvement and account requirements are checked for each market and workload.
- 1
Share the workload
Customer + TitanBases
Provide AWS Account ID, use case, architecture and services, estimated usage and success criteria.
- 2
Review program fit
TitanBases
TitanBases checks applicable AWS programs, evidence and benefit type. Eligibility and approval remain program-specific.
- 3
Validate with AWS where appropriate
TitanBases + AWS
For workloads estimated at USD 5,000+ monthly AWS usage, coordinate an AM/SA discussion as appropriate; this is not an AWS funding threshold.
- 4
Submit and track the request
TitanBases + customer
Confirm account and program details, submit through the applicable process, respond to feedback and verify any approved benefit before relying on it.
- 5
Run and accept the PoC
Customer + TitanBases
Test against agreed criteria, record results, usage and open risks, then decide whether to revise, stop or plan a production handoff.
AWS PoC process at a glance
The five stages below summarize the request path. AWS participation and any program support are reviewed for each workload and market.
Program review, timing and further reading
Program classification must reflect the real workload. Two categories used in TitanBases working references are AWS Migration & Modernization and AWS Native Consulting and Implementation. We verify the current product code in the applicable AWS process; a code does not establish eligibility or speed up approval. For complete requests proceeding to program review, 15-25 days is a planning estimate for a decision and, where applicable, customer credits in the designated AWS account. Timing and funding type vary by program and market. Some support is partner-side cash rather than customer credits. Do not rely on unapproved benefits. The technical PoC guide, cost and timeline article, funding guide, and AWS Partner page below provide the detail behind this intake process.
Explore the AWS PoC resources
Use the detailed guides for implementation, budgeting, program differences and partner validation. This landing page remains the starting point for a specific request.
AWS PoC implementation guide
Technical scoping, testing and the path to production.
Learn moreAWS PoC cost and timeline
Budget and schedule drivers for a defined workload.
Learn moreAWS credits and funding
How programs differ, with eligibility caveats for Vietnam.
Learn moreAWS Partner in Vietnam
Verify TitanBases partner status and service scope.
Learn moreAWS PoC FAQs: Vietnam and global teams
Answers about starting an AWS proof of concept, program review, credits and acceptance. Program terms and AWS involvement are confirmed for each market.
How do we start an AWS PoC in Vietnam or another market with TitanBases?+
Send the AWS Account ID, account root email, use case, proposed services and acceptance criteria. TitanBases reviews the workload, relevant programs and next steps. Program availability and delivery scope are confirmed for each market. Never send credentials.
Do we need a completed architecture or a new AWS account?+
Neither is a universal prerequisite. Share the current account and known constraints, even if the design is preliminary. We clarify architecture, the account used for the PoC and success criteria during scoping. Each program may have separate account eligibility requirements.
What does TitanBases do, and when does AWS join the PoC discussion?+
TitanBases helps define scope, assess program fit, prepare the request and plan implementation and acceptance. For workloads estimated at USD 5,000 or more in monthly AWS usage, we can coordinate an AWS Account Manager and Solutions Architect discussion when appropriate and available. This is our coordination practice, not a universal AWS eligibility threshold.
Does an AWS PoC request guarantee funding or customer credits?+
No. Eligibility, benefit type and approval depend on the workload, program and AWS. Submitting this form is not AWS approval. Some benefits are partner-side cash, not customer credits. The funding guide in Related Resources explains program distinctions.
If customer credits are approved, which account receives them and when?+
We confirm the designated AWS Account ID and help verify any approved customer-credit benefit under its program terms. For a complete request proceeding to review, around 15-25 days is a planning estimate, not an AWS commitment. Timing varies by program, review stage and missing information.
How do we decide whether the AWS PoC succeeded?+
Agree on the target workflow, measurable technical and business results, security and integration constraints, test evidence and a decision owner before implementation. The outcome is a recorded decision to revise, stop or plan production, not merely a working demo.
LET'S TALK
Request an AWS PoC scope review
Share the AWS account and workload details. TitanBases will review the scope and contact you about the next step. Do not include credentials or customer data.