Skip to main content

When to Hire a Software Boutique

My company InfoStrat is a software boutique.  We're a small company that specializes in several related areas, especially on developing line of business solutions on the Microsoft platform.  I'm often asked why organizations should hire our company rather than a large systems integrator or a staffing company.

A boutique usually consists of permanent, fulltime employees who are organized in teams to tackle a project.  This is different from a staffing company that focuses on gathering resumes of qualified individuals and adding them to a team in another organization.  The team has worked together and knows each person's strengths and weaknesses.

Specialization allows boutiques to stay up to date with the latest technological advances in their area, and they often have more experience in their specialties than generalists. The advantage of a large systems integrator is that their staff covers a much wider set of skills and technologies than any boutique.

Boutiques often have higher hourly rates than staffing companies or global system integrators.  If you are looking for the lowest rate and do not need a team to conduct a project, offshore developers and staffing companies are usually the cheapest.  Global integrators have a wide range of rates, and tend to apply a larger number of hours and people to a task than would a boutique.

Staffing companies do not assume the risk for a project.  They provide people and you are responsible for rejecting them based on their performance.  Boutiques rely on referrals for new business, so they are the most zealous in making projects succeed. 

Here is a table that compares these options:


 
Global Systems Integrator
Staffing Company
Offshore Development
Boutique
Hourly rate
High
Medium
Low
High
Geographic reach
High
High
N/A
Low
Accountability
High
Low
Low
High
Deep pockets
Yes
Maybe
No
No
Specialized
No
No
No
Yes
Mature project processes
Yes
No
No
Yes
Invests in people
Yes
No
Yes
Yes
Strong communication skills
Yes
Maybe
No
Yes

In many cases, the best solution is a team of companies that consists of large integrators and boutiques.  Some of our most successful collaborations have been with global systems integrators such as HP, SAIC, and Lockheed Martin.  The large integrators have broad skills that complement our specializations and their geographic reach is vital for large projects with multiple locations.

Popular posts from this blog

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of .onmicrosoft.com such as acme.onmicrosoft.com.  User accounts belong to a tenant, and subscriptions are assigned to user accoun

Understanding Dynamics 365 and Office 365 Admin Roles

Managing Dynamics 365 instances If you run Microsoft Dynamics 365 (formerly Dynamics CRM) in the Microsoft cloud, you need to understand how your Dynamics instances relate to Office 365 and choose which of your administrators receives which roles and permissions to manage Dynamics 365. In on premises deployments, your network administrator would create and delete user accounts.  The Dynamics 365 admin would then assign permissions to users in Dynamics 365. This post explains three administrator roles: Office 365 Global Administrator Dynamics 365 System Administrator Dynamics 365 Service Administrator You may think that the Dynamics 365 system administrator would have power to do all the actions needed to manage Dynamics 365, but this is not the case. What's different in Microsoft cloud deployments is that licenses and user accounts are managed in Office 365 by an Office 365 Global Administrator.  This role is analogous to a network administrator for an on premises

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do not require advan