Dealing with a CMS as the source content repository can be quite cumbersome and challenging for a vendor, but the fact that it’s also an uncertain territory for customers creates a succulent business opportunity for those translation agents willing to invest and persevere in differentiating themselves through technology. In this presentation, we will have a look at what it takes to build a workflow around your customer’s CMS and your existing tool ecosystem that (without breaking the bank) delivers the kind of efficiency and automation that, until recently, seemed only within the reach of the bigger players (and pockets) in our industry.

1. Threefold integration:
CMS, TMS, and CAT
Jose Palomares, CTO at Venga

2. #UTICamp
About Venga
•Multilingual vendor
•In-country translators
•End client-driven
•24/6, 7 locations, 3 continents
•Follow the sun workflow

3. #UTICamp
Why listen to me?
• It’s very polite of you. It shows good manners.
• 18 years of experience on both client and vendor side.
• I work with people smarter than me
• IT
• Localization engineering
• Technology development
• Use technology as a differentiator.

4. #UTICamp
CMS galore

5. #UTICamp
Watch the competition
They may tell you where the money is

6. #UTICamp

7. #UTICamp
What do my prospects use?
www.builtwith.com

8. #UTICamp
Integration, why?
• Customer user experience (UX)
• We hate copying and pasting
• We hate emails & attachments
• We hate slow, tricky & repetitive
• We hate waiting
• Efficiency
• We love less human errors
• We love less clicks-to-action
• We love shortening timelines
• We love reducing overhead
• Business reasons
• Business enabler
• Competitive advantage
• Deep involvement with client
• Charging more, not less

9. #UTICamp
The Holy Grail of Translation Integrations

10. #UTICamp
Zero-Management Human Translation
Client request
• Analysis
• Leverage
• Quote
• Approval
Project creation
• Availability request
• File processing
• TMs, Glossaries, Filters
• Assignment: Individual,
FirstAccept, Prioritized
T+E+P, push
• Pre-translation or
Pseudo-translation
• Auto analysis
• Auto QA
• Archiving & clean-up
Delivery
• Push/pull to CMS
• Import
• Staging URLs
CMS + API
TMS / CAT
TMS / CAT
API + CMS

11. #UTICamp
Ingredients
• 3 table spoons of talent, internal
and/or external
• 2 cups of slow times
• 1 pint of persistence
• A generous handful of euros
• A pinch of luck
• A big bucket of patience

12. #UTICamp
Step-by-step instructions
• Name your champions
• Product manager (internal)
• Tool experts
• Internal/external validators
• Internal/external dev team
• Research CMS + API
• Has an API? Open? API Docs?
• Done before? By whom? How
long, how much, how well?
• Development plan
• Realistic cost & timeline
• Agile!

13. #UTICamp
How Venga does it
Client request
• Analysis
• Leverage
• Quote
• Approval
Project creation
• Availability request
• File processing
• TMs, Glossaries, Filters
• Assignment: Individual,
FirstAccept, Prioritized
T+E+P, push
• Pre-translation or
Pseudo-translation
• Auto analysis
• Auto QA
• Archiving & clean-up
Delivery
• Push/pull to CMS
• Import
• Staging URLs
CMS + API
TMS / CAT
TMS / CAT
API + CMS
CMS + Client Portal
XTRF
memoQ
templates +
Checkmate
scripts
CMS
partnership +
Custom
code
US
ASIA
EUROPE
US

14. #UTICamp
Set it up once, repeat as needed

15. #UTICamp
Some advice
• Understand it well so you/they can build/sell it well
• Leverage what you already have in your toolset
• Go with the flow  Mainstream connectors (biz enablers)
• Don’t go with the flow  Niche opportunities (biz growers)
• CMS / TMS / CAT  If it doesn’t have an API, stay away
• If the CMS vendor is not friendly/helpful, stay away
• Flex, stretch, repeat. It gets much easier after the first time.

16. #UTICamp
Thanks for your attention
Jose Palomares
CTO, Venga Global
jose.palomares@vengaglobal.com
@localizing