Service Offerings

We have four key pillars through which to deliver value.

circulo a

Services 1

Fully staffed projects in Mexico
(Nearshore Development Model)

•Effectively extends the capability of the company's internal development function

•Option for full responsibility for a project or group of projects
Custom team assembly. Operates as an extension of the client, normally under the leadership of a PM or Scrum Master

Services 2

Targeted Staff Augmentation
(Onsite, Remote or Hybrid )

•Supports a client’s innovation and development efforts by filling specific area of technical need
•We can provide engineers that tightly collaborate with the
clients' internal teams.
•Availability of high quality "remote internships" of various levels and skills sets (undergrads and grad students).

Services 3

Testing Services & QA
Nearshore Application Validation

Extends the testing capacity of the customer by providing the following services:

Stress and Load Testing.
•GUI and usability.
Security and penetration testing.
•White & Black box QA testing.

Services 4

Process & Project

•Business Process Analysis & Improvement.
•Requirements Management.
Project/Portfolio Planning
•Architecture (Technical & Functional alignment).
PMO Initiation and Management.
•Best Practices & Benchmarking

Areas of Expertise

Our background and experience allow us to understand the business intent, as well as the underlying technologies that enable it.

Areas of expertise


Core Technologies / Software• Architecting, Programming and Testing • Object Oriented technologies: C++, Java, J2EE
• Net and Windows technologies • Scripting: PERL, Python, Javascript
• Mobile technologies: Brew, Windows Mobile, Android, iOS, Obejctive C • UI design and development
• Content Management: Sharepoint, Adobe • Web Applications


Core Technologies / RDBMS•Oracle • SQLServer • MySQL • Postgres


Verticals•Electronics and High Tech • Software
• Physical Distribution and Logistics
• Discrete manufacturing • Banking and Financial Services
Our Methodologies and Frameworks

At Rightsource, we firmly believe that in addition to technical talent, a critical success factor is an adequate, and properly agreed upon engagement model and process
(fundamentally an agreement on the way in which work will be done).

Areas of expertise
Software Development
  • Waterfall SDLC
  • Agile Scrum
  • Hybrid models
Other Reference Practices
  • ITIL
  • Lean Six Sigma
Process & Quality

Leveraging Total Quality and Lean principles, we strive to establish clarity of purpose, using a data driven approach,
while maintaining a customer-centric perspective for all projects:

1.Understand. We make it a point to spend the time required to truly understand the clients problems and their business intent. We want to go beyond a discussion of features and formats to provide deeper value. Experience has shown us that this investment pays off many times over given the additional clarity it provides.
2. Agree. Formal agreement on how the team(s) will work on a particular engagement (both structure and method). This step is critical and frequently overlooked; we jointly acknowledge the way the client conducts work currently, and either modify it or adapt to it; no theoretical framework will replace this.
3.Establish: Depending on the engagement type and project size, we also look to hold at least one in person meeting prior to development. We work with our clients up front to jointly define success and when an effort will be “done”.
4.Perform: We then move into what we like to call “Trust Based Execution”. It is considered paramount to maintain a healthy communication “cadence” for the duration of the effort. We believe in a balanced ‘trust but verify’ approach.
Engagement Models

We are pragmatic in the use of different models that can be customized as required by specific client and project needs.

circulo a
Typical engagement flow for agile (SCRUM)

Typical engagement flow for agile (SCRUM)

US-India: 14003 km + 22 hrs + ~$10k+ (a 7 day stay minimum)

Client Team

US-India: 14003 km + 22 hrs + ~$10k+ (a 7 day stay minimum)

Rightsource Team
More About Distributed Agile…

Physical co-location is the best arrangement for Agile development, however, it is indeed possible to establish high performing
Agile teams in a distributed setting by rigorously following some key guidelines:

Typical engagement flow for agile (SCRUM)

  • • Agreement on working mechanics (wit disciplined communication cadence)
  • • Ensure trust is built across the teams
  • •Leverage methods and technology consistently (eg. use flexible telecomm setups)
  • •Appoint single engagement lead at each site (Scrum Master, Product Owner, and/or Project Manager);
  • •Have a reasonable overlap of working hours.
Typical Communication Cadence
Type of Communication Frequency Comments
Daily scrum standup* Daily Progress, Blockers and Action Plan
Status Reporting (Case Management) Weekly Weekly meaningful metrics/reports shared with Client
1st Level Management Review Bi-Weekly/Monthly Support Manager meets with client manager for updates/review
Quarterly Engagement Review Quarterly Executive Strategy and Performance Review Meetings
Why nearshore?

In reality, if cost is not a key factor and talent is available, you may want to keep development in - house, or outsource onshore to a lower cost US location
(it is nevertheless advisable to keep it within 2 time - zones of the core business team, even in the US)

circulo a

why nearshore a

In other cases, there are circumstances where an existing offshore support operation such as India is delivering the proper level of service and with adequate costs. There will also be some projects that are well suited for a traditional waterfall approach and will work well through existing remote teams. In these cases, there may not be a need for a change in model.

why nearshore b

However, a more iterative approach or more frequent communications will frequently be required. A committed Nearshore team will provide a better alternative in these cases:

  • Physical proximity and similar time zone
  • Cultural compatibility and ease of doing business
  • Cost savings through lower Total Cost of Engagement
Drivers for nearshore

Nearshoring: “The practice of bringing production and consumption centers closer together, with the goal of generating logistical,
transportation, and communication benefits to multinational commerce.”

(Push Factors)
  • Offshore fatigue
  • Risk Mitigation
  • Delivery Diversification
  • Client Demand
  • Increasing Offshore Costs
  • Slow Infrastructure Development
  • Restrictive Trade Practices
  • Taxation Overlaps
(Pull Factors)
  • Proximity (Distance, Time Zone)
  • Expanding Talent Pool
  • Growing Domestic Market
  • Lower Talent Movement Barriers
  • High Growth Rates
  • Geopolitical Stability
  • NAFTA, Free Trade Agreements
  • High Concentration of Young Population

* Push factors are reasons why vendors/buyers look to diversify out of current geographies, while Pull factors are reasons why vendors / buyers look to Nearshore as a delivery platform.