Este artículo solo está disponible en inglés por el momento.
Microsoft Office Add-in Development: Company Comparison Guide

Microsoft Office add-ins put your own tools inside Word, Excel, Outlook and PowerPoint, where people already work. A contract template generator in Word, a pricing model in Excel that pulls live data, an Outlook add-in that files emails into your CRM: each removes copying and pasting between systems. Building them well needs specific experience with Microsoft's platform, so choosing the right development company matters.
What Office add-ins can do
- Word: insert clauses and templates, fill documents from a database, check documents against rules, manage content controls.
- Excel: custom functions, data connections to internal APIs, task panes for data entry and validation.
- Outlook: act on the open email or meeting: save to CRM or case management, add tracking, insert templates, schedule with rules.
- PowerPoint: brand-approved slide libraries and automated deck generation.
Modern add-ins use the Office JavaScript API (Office.js) and web technologies, and run on Windows, Mac, the web and, for Outlook, mobile. Older VSTO and COM add-ins run only on Windows desktop.
How to compare development companies
1. Real Office.js experience
Ask to see add-ins they have shipped, ideally running. Office.js has platform differences between Windows, Mac and the web, API requirement sets and quirks that only experience teaches.
2. Identity and Microsoft Graph
Most business add-ins need single sign-on with Microsoft Entra ID (Azure AD) and calls to Microsoft Graph or your own APIs. Ask how they handle authentication, consent and token handling.
3. Deployment and AppSource
Internal add-ins are usually deployed centrally through the Microsoft 365 admin centre. Public ones go through AppSource validation. Ask which they have done and what problems they hit.
4. Security
Add-ins often touch confidential documents and email. Look for least-privilege permissions, no unnecessary data leaving the tenant, and clear data handling terms.
5. User experience inside Office
A task pane is narrow and users are busy. Good add-ins follow Fluent UI, load quickly and do one job clearly.
6. Maintenance
Microsoft updates Office continuously. Ask how they test across Office versions and what support looks like after launch.
Migrating from VSTO or VBA
Many organisations have VBA macros or VSTO add-ins that only work on Windows desktop. Rebuilding them with Office.js lets them run on Mac and the web, and makes central deployment easier. A good partner will tell you which features can be ported directly, which need a different approach, and which are not possible in Office.js today.
Timeline and cost
A focused add-in with a task pane, single sign-on and one or two integrations typically takes a few weeks to a couple of months. Larger add-in suites with document automation across several Office apps take longer. Cost follows team size and duration, and an offshore team in Sri Lanka keeps it well below Western rates.
Questions to ask
- Which add-ins have you shipped, and for which Office apps?
- How do you handle SSO and Graph permissions?
- How do you test on Windows, Mac and the web?
- Have you deployed through AppSource or centralized deployment?
- What happens when Microsoft changes an API?
Office add-ins with Mickiesoft
Mickiesoft builds Microsoft 365 add-ins for Word, Excel and Outlook using Office.js, with Entra ID sign-in and integrations into clients' own systems. Tell us what you want to automate inside Office.
Ready to accelerate your project?
Contact Mickiesoft today for a free technical consultation.
Contact UsPreguntas frecuentes
Encuentre respuestas a las preguntas más habituales sobre nuestros servicios, nuestro proceso y nuestras capacidades.