_edited_edited.png)
Our Story
Conventional Industry wisdom says that you shouldn’t ship your org chart, but where does that leave your offshore investment? The decision to send some work offshore is usually done for economic reasons; and with a good understanding of exactly how this will affect things like deployment or how the work is done on a day to day basis, this can pay off earlier than later.​If your architecture is already sufficiently decomposed like microservices or several of the event-driven flavours, it will be very easy to just ship the entire component or service and put the offshore team in charge of integrating it with the rest of the system. Many projects though, for many great reasons, aren’t structured like this; and re-architecting your application so you can make use of offshore software development might not reap the dividends you planned for. If you have an application with many component-level as opposed to service-level dependencies, for instance, communicating at punctuated time windows at the start or end of the day is the best recipe we know for a frustrated dev team.
Our mission
To Let Offshore Engineers Realize Most Of The Value Of The Work They Do, Having A Transformative Effect On Their Community.
People Shouldn’t Go Offshore Because It’s Cheap, People Should Go Offshore Because It’s Good.
​
There’s no secret to success, getting good productivity from an offshore team is about communication. More monolithic applications require almost realtime communication, while SOA-style applications can happily chug along with coarser or even communication done entirely over email. A popular solution to this problem is to have two folks — typically PMs — overlap with the other team, which can work, but typically just generates more meetings. (What did they mean? can you set up a call with the dev?, etc.) Our architects are entirely technical experts that will straddle both timezones, work on the same codebases, and have work-item level knowledge of tasks and issues. There is no signal loss due to being a level of abstraction removed.
These are of course, just some of the issues that we’ll help you move through, but drop us a note, and we’re happy to chat over zoom to see if we can help.
Our engineers
​
✓ Are architect level
✓ Are experienced team leads
✓ Have extensive side projects
Therefore
​
✓ We don’t need to keep a bench, we hire on demand, keeping our overhead low.
✓ They never worry about the next gig. There is always room for good people.
✓ We’re all often aware of interesting projects that need people.
