First, it might pay in the long run to have someone else flesh out your bpo leg:
Are you already in-process?
Is this to satisfy proof-of-operation for venture capital?
What is your data system?
Do you want to tie database entries into a flowchart of business rules?
I would expect that you are looking for a procedural modeller (that uses a database to store elements) rather than a template for Access or SQL Server:
Most new bpo's already have plans similar to those shown here:
and then add import/export hierarchy to it. Once that is done, you can add auditing and triggering for bpo beyond the standard people/inventory/sales/accounting structure that every dbms has in their samples.
To roll your own, you need to gather a project team to manage just this project. The other team members would hopefully be your company's sme's (local topical experts) in the areas mentioned above. Also, an attorney to verify best practice for offshore agreements would be necessary at the beginning, not just the end, in case by-laws and trade agreements will affect what you can produce or how you produce it.
Sounds like fun,