Request a proposal and ProVizion will send a written plan for your team: structure, management model, timeline and terms, built around your roles, hours and systems.
Trusted by teams at
Fields marked optional can be left blank. Rough answers are fine; we will ask about anything we need clarified before we write.
A member of our client team will read it and reply within one business day, usually with a few questions before we write your proposal. If you would like to talk it through sooner, pick a time on our calendar.
Book a call →When you request a proposal, most Philippines outsourcing providers reply with a brochure and a rate card; ProVizion replies with a document built around your roles, your hours and the systems your team will work in. The form on this page collects what we need to write that document properly. It takes a few minutes if you have the basics to hand and there is no obligation attached to submitting it.
We have prepared proposals for organisations as varied as Hewlett Packard, Symmetry Financial Group and Quility, and for single-seat requests from businesses hiring their first offshore assistant. The questions are the same in each case because the answers are what determine whether a team works. Below, each section of the form is explained so you know why we ask and what we do with the answer.
Every proposal we send sets out four things. First, a team structure: the seats, their shifts in your time zone, the skills each requires and how they report. Second, a management model: whether day-to-day direction sits with you or with a ProVizion team leader who runs rosters, quality and coaching, with a note that you can change this later. Third, a timeline from signature to go-live, which for one to three people can be as short as 48 hours after the candidate is chosen and for large programmes runs to a few weeks. Fourth, terms, including the contract length, which typically sits between three and twelve months depending on scale, and a plain statement of what is included and what is billed separately. If you want to understand the factors behind that last section before you receive it, read our page on what shapes an offshore team quote.
"Very professional group, highly recommend their services!"
Describe each role in your own words. A job title helps, but a sentence about what the person will actually do each day helps more, because the same title means different things in different businesses. Tell us whether the work is customer-facing or internal, and whether it needs any licence, language or technical background. If you are not sure how to split the work into roles, say so and describe the work instead; designing the split is part of what the proposal does.
Tell us the coverage window in your local time and the days of the week. Manila is UTC+8, and we will translate your hours into the appropriate Manila shift. Then estimate volume: calls per day, tickets per week, applications per month, or whatever unit fits. A rough figure is fine. Volume tells us how many seats the work justifies and whether the roster needs to flex around a weekly or seasonal peak.
"Great team that performs for us. Game changer."
List the platforms the team will work in, such as your CRM, helpdesk, phone system, practice management or accounting software. Our staff work inside client systems rather than ours, so knowing the tools lets us recruit people who already use them and plan role-based access from the start. If your data falls under PCI DSS, HIPAA, GDPR or a similar standard, tell us here; we can structure the engagement to meet those requirements, and it changes how the team is set up.
Tell us which countries your customers are in, because accent, cultural familiarity and regulatory knowledge all follow from that. Give a preferred start date, even a rough one, so we can check recruitment lead times for your skill set. Finally, indicate whether you would prefer to run the team in-house or hand the daily supervision to one of our team leaders. If you have no preference, say so and we will recommend one based on the roles. The full sequence that follows a signed proposal is described on our process page.
Submissions are read by a person, not a queue. You will typically hear from us within one business day with any questions we need answered before writing. The proposal itself follows a few days after that, sooner for straightforward single-role requests and a little longer for multi-team programmes that involve partner facilities. If you would rather talk before committing anything to a form, the contact page explains how to book a video call instead.
Yes. Single-seat proposals are common and receive the same attention as larger ones. Many of our longer relationships began with one assistant or one support agent, and the proposal makes it clear how the team could grow if the first hire works out.
No. It is a considered offer based on the information you provide, and you are free to compare it with others or take no action. If you proceed, the proposal becomes the basis of a contract, which we then finalise together with any adjustments from the discovery conversation.
Give your best estimate and say it is an estimate. We would rather size a team conservatively and add seats than overstaff from the start. If you have any historical data, such as call logs or ticket exports, attaching it is helpful but not required.
Yes. We list what is included and what is billed separately so you can compare our document with others on a like-for-like basis. Ask any other provider to do the same before you compare headline figures.
Proposals carry a validity date, usually a few weeks, because recruitment conditions and market salaries move. If you need more time to decide, let us know and we will confirm whether the terms still stand or issue a refreshed version.
Two ways to start. Book a short call, or request a proposal and we'll come back with a recommended team structure.