At the start, if agreed
An initial invoice may be due before work begins. Any initial payment requirement is stated in the agreement.
Working with Evolext
From your first question to a clear next decision.
A step-by-step view of a post-quantum engagement: the conversations, evidence, agreements, delivery, and billing that connect an inquiry to scoped work.
Proposed engagement process
Four phases. A clear handoff at each one.
Start with the evidence and decisions you already have. An inventory, assessment, or prototype can be a separate engagement; you do not need to purchase every stage.
This is a proposed working process. Your accepted proposal defines the actual scope, schedule, fees, handling arrangements, and payment terms. Evolext currently focuses on research, assessment, and controlled laboratory prototypes.
Phase 01 / Step 01–03
Start a conversation
Establish the question, the system, and whether there is a suitable starting point.
Send a high-level inquiry
- Your part
- Describe your system, the decision you need to make, and any known constraints. Keep repositories, credentials, keys, and confidential reports out of the inquiry form.
- Evolext’s part
- Review the inquiry and its selected service, if any.
- What you leave with
- An initial question for Evolext to review.
Check the fit
- Your part
- Clarify any missing high-level context by email.
- Evolext’s part
- Review the objective against the studio’s current research, assessment, and laboratory prototype scope. Arrange a conversation, request clarification, or decline.
- What you leave with
- A decision on whether to continue to discovery.
Discuss the starting point
- Your part
- Bring a system outline, known owners, data lifetimes, dependencies, and the decision you want to support.
- Evolext’s part
- Discuss the objective, vendor constraints, available evidence, and a suitable starting service. Explain the limits of the proposed work.
- What you leave with
- A shared problem statement and a possible first engagement.
Phase 02 / Step 04–06
Agree the engagement
Set the evidence boundary, deliverables, responsibilities, and commercial terms before work starts.
Agree how evidence is handled
- Your part
- Identify authorized providers and recipients of evidence, access restrictions, and any required handling arrangements.
- Evolext’s part
- Agree what can be collected, approved access methods, and expected retention or deletion arrangements before collection. Use approved exports where sufficient.
- What you leave with
- A recorded boundary for evidence collection and handling.
Review a scoped proposal
- Your part
- Review the deliverables, exclusions, your responsibilities, review points, schedule, price, and billing milestones.
- Evolext’s part
- Propose a bounded first stage. Where the question is broad, consider inventory or assessment before separately scoping a prototype.
- What you leave with
- A concrete proposal you can accept, revise, or decline.
Confirm terms and authorization
- Your part
- Confirm authorized contacts, scope, acceptance and change processes, and payment terms. Complete any agreed initial payment.
- Evolext’s part
- Confirm the engagement and any agreed initial invoice. Begin work when the required agreement, authorization, and agreed payment conditions are met.
- What you leave with
- An authorized engagement with a defined commercial starting point.
Phase 03 / Step 07–09
Build the evidence
Investigate the agreed scope and progress to testing only when the use case and support justify it.
Build or review the inventory
- Your part
- Supply approved evidence and help confirm owners and system context. Existing suitable inventory evidence can be used as the starting point.
- Evolext’s part
- Review cryptographic uses, dependencies, sources, owners, and gaps within scope. Scanner observations require human review and do not establish complete coverage.
- What you leave with
- A bounded inventory and unresolved questions, if inventory is in scope.
Assess and prioritize
- Your part
- Validate business priorities, confidentiality lifetimes, interoperability needs, and decision owners.
- Evolext’s part
- Review impact, vendor support, dependencies, and operational constraints. Identify what to investigate, defer, or consider for testing.
- What you leave with
- A readiness summary and prioritized roadmap, if assessment is in scope. The engagement can end here; a prototype is optional.
Test a suitable candidate
- Your part
- Agree one use case, representative test conditions, and acceptance criteria for a separately scoped laboratory prototype.
- Evolext’s part
- Record the applicable standards, supported implementations, test environment, and limits. Test relevant compatibility, performance, failure, and recovery questions.
- What you leave with
- A prototype record with observations, untested cases, limitations, and a next decision. Production work requires separate scope and authorization.
Phase 04 / Step 10–12
Review, close, and revisit
Review the work, complete agreed billing milestones, and decide whether further work is useful.
Review and receive the work
- Your part
- Review the agreed deliverables within the agreed review period and raise corrections or acceptance questions.
- Evolext’s part
- Walk through observations, evidence gaps, residual risks, and next actions. Address corrections covered by the scope.
- What you leave with
- Accepted deliverables or a documented list of outstanding acceptance items.
Complete billing and close
- Your part
- Review invoices against the agreed scope and milestones, and pay according to the accepted terms.
- Evolext’s part
- Invoice at the agreed milestones, record payment status, and complete the agreed delivery and handling closeout. Billing may also occur earlier in the engagement.
- What you leave with
- Final engagement records and completion of the agreed commercial obligations.
Revisit when there is a reason
- Your part
- Return when dependencies, vendor support, requirements, or the decision change.
- Evolext’s part
- Agree a new objective, deliverables, and price before any further assessment, testing, or separately scoped engineering begins.
- What you leave with
- An optional new engagement when further work is useful.
Billing follows the agreement, throughout the work.
These are possible invoice points, not a fixed package or payment policy. The accepted proposal states which apply, the amounts, payment terms, and the delivery or acceptance trigger.
At agreed milestones
A completed inventory, assessment, or other agreed milestone may have its own invoice. Later stages require their own agreed scope.
At delivery or acceptance
A final invoice may follow the delivery or acceptance milestone specified in the agreement. Resolve outstanding acceptance items through the agreed process.
Each invoice should identify the engagement, the agreed milestone, the amount, and the payment terms. This page does not provide checkout or take payments.
An engagement can finish at the decision you need.
Inventory may be enough to identify the next questions. An assessment may justify deferring a change. A prototype may show that a candidate needs revision or should stop. Progress depends on reviewed evidence, not completing every service.
Bring a question, a system outline, and a boundary.
Keep the first inquiry high-level. Identify the decision, known owners, available non-sensitive evidence, and access constraints. Scope, schedule, and fees are agreed after reviewing the requirements.
Inquiry details have the website’s Supabase and LINE handling. Technical evidence collection needs separately agreed arrangements.