Engagement FAQs
Straight answers to the questions buyers ask most when comparing engagement models: how they differ, how work is priced and changed, who owns the result, how teams communicate and what happens at the end. Where an answer depends on the project, it says so and explains why.
Start your project
Choosing a model
Which engagement model should we start with?
A project-based engagement is often the clearest way to begin: a defined outcome, written scope and acceptance criteria. Dedicated teams suit ongoing, evolving products. Partnerships suit new products, and managed services suit operating live systems.
Can we change model later?
Yes. A common path is a project to build a first release, then a team to evolve it, then managed services to run it. The terms of each stage are agreed when it begins.
Is a trial or pilot possible?
A small, scoped first stage, such as discovery or a pilot release, is a sensible way to test fit. The scope and outputs are agreed in writing.
Pricing and estimates
Estimates reflect scope, complexity, integrations, quality targets and team mix. A fixed price suits a well-defined scope; a time-and-materials or capacity model suits scope that will evolve. Estimates are ranges until the unknowns are understood, and assumptions are written down.
Request a proposal when you can describe the outcome, or ask for a short discovery if you cannot yet.
Scope and change
- Scope and acceptance criteria are written before build starts, and every material change goes through a recorded request.
- Defects against agreed criteria are fixed as part of the work, while new requirements are changes.
- In agile engagements, priorities change freely within agreed capacity and budget.
- Both sides see the effect of any change on cost, time and risk before agreeing it.
Share the outcome you need and Renvric will recommend the smallest useful next step.
Ownership and confidentiality
Intellectual property in work created for you is assigned to you under the agreement, with any reusable provider components identified and licensed clearly. Confidentiality terms are signed before sensitive material is shared, and access to systems is limited to the people who need it.
Your legal advisers should review the contract; Renvric is glad to discuss the terms.
Working together day to day
How often will we hear about progress?
Typically weekly written updates plus regular demonstrations, with risks raised as soon as they are known.
Who is our main contact?
A delivery lead, supported by a technical lead, with a named senior contact for escalation.
How is time zone difference managed?
With a regular overlap window and written summaries, agreed at the start.
Quality, security and launch
Related areas to explore: Compare Engagement Models, Large language models and Customer engagement platforms.
- Definition of done, automated testing and code review are standard in the delivery process.
- Security requirements are agreed at the start and tested before release.
- Release plans include rollback arrangements and agreed go-live responsibilities.
- Evidence such as test summaries and release notes is provided with each release.
Common questions
What is the simplest way to start working with Renvric?
Describe the outcome you want and the constraints around it. Renvric will suggest a first stage, often a discovery or a defined project, and provide a written proposal with scope, assumptions, acceptance criteria and commercial terms for your review.
Do you work on fixed price or time and materials?
Both are possible. Fixed price suits a well-understood scope with clear acceptance criteria. Time and materials or a capacity model suits evolving work. The right choice depends on how certain the requirements are, and the reasoning is discussed in the proposal.
What do we need to have prepared?
A description of the problem or goal, your constraints on time and budget, key stakeholders and any existing systems or documents. If you do not have these, a short discovery can establish them, producing a scope you can use with any provider.
What happens if our needs change during the work?
Changes are raised, assessed for cost, time and risk, and decided by your named approver before work proceeds. In agile engagements, priorities shift within the agreed capacity. Either way, the change and its effect are recorded.
Who can I contact with a question not covered here?
Write to info@renvric.com with your question and context, and the appropriate person will respond. If you already have a delivery lead, they are the quickest route for questions about your project.
Other ways to work together
Support after launch, knowledge transfer and handover are planned during delivery, not left to the end. You can keep Renvric for support, take everything in-house, or use a mix. Documentation, credentials and repositories are yours throughout.
Still have a question that is not here? Ask us, and we will answer plainly.