Got Questions? You’re Not Alone.
Frequently Asked Questions
- What’s the difference between Localshoring™ and contracting a developer?
Contracting or hiring a developer involves integrating a developer into your organization and managing not only the developer but also the project lifecycle by yourself throughout the software development process. Localshoring™ is a team development effort managed by SEQTEK’s product owners, which involves SEQTEK taking on the responsibility of delivering the software product, thus leaving you to manage the outcome, NOT the process.
- Does Localshoring™ cost more?
Yes during the project, no for your long-term business. If your company hires three developers and you manage the software development cycle, your company is out the cost of three developers and some sort of manager. This is a pretty standard setup. A Localshoring™ development is a team effort within SEQTEK. The project always includes a product owner / business analyst that understands your goals and communicates those to the rest of the team. Any number of developers, UI/UX designers, QA/testers, CI/CD engineers or systems engineers could be involved depending on the project need. As an example, the project may have two full-time developers and then a fractional tester and a fractional designer and at the beginning and end of the project we would pull in systems engineers to build out the cloud deployment. Whereas internally your company may attribute only three developers to your project, for a Localshoring™ project, that average would most likely be three and a half to four contractors. So, we acknowledge that during a project our costs are going to be more costly than internal development. However, and this is a major advantage to our team development, since our teams grow and shrink and disappear as needed, our costs are finite. In fact, we are so sure of this, we offer a guarantee for our delivery of completed code. Additionally, internal development teams tend to have lingering support work on products that are delivered. Obviously this is a generalization, however we see it often enough, that we feel comfortable pointing it out. For a SEQTEK project, when we are done, we must be done. Therefore, the testing, deployment and delivery looks different to you. Our product deliveries must be a complete set of work since we won’t be there tomorrow “to just do one more thing.”
- Do you develop for the cloud?
Yes. In fact, we were developing for the cloud before the cloud was cool. The founders were part of the Internet story in the mid-’90s and have been developing for the cloud from the beginning of SEQTEK. The first project ever built by SEQTEK was for the Internet and every project since.
- How does Localshoring™ affect project management?
SEQTEK created the Localshoring™ concept to provide our customers an expedited development process over traditional methods by minimizing your management effort. We work in teams and take over responsibility for the project, delivering proven quality work in less time. That way, you manage an outcome, not a complex process.
- Does SEQTEK use an Agile Development Methodology?
Yes, we use a modified Agile Development Lifecycle, which allows us to work with you through our Product Owner/Business Analyst program. With check-ins every two weeks that include working code, we demonstrate progress while allowing you to focus on your business. This helps us work efficiently and maximize output for the least amount of effort.
- What is your development life cycle?
Our process for each project consists of the same three basic steps: Discover, Develop and Deploy. Discovery allows us to understand your business, user and technical requirements. Development is a cycle of continual development, testing and deployment within our secure environment—automated using GitHub paired with AWS or Azure. Every two weeks, the product owner on our team completes a review within our staging environment of what was done by the team so that our customers receive full transparency into what is accomplished. Once the initial development is complete, we engage with the customer for a full User Acceptance Testing process, then our team deploys to production. Initial development starts by moving code from our development area to a staging area where ongoing user testing is done. After an initial production deployment, we can deploy to production every two weeks or earlier, depending on the organization’s strategy.
- How do you bill?
We bill monthly based on work performed. One of the advantages of Localshoring™ is using only what’s needed—like testing or bringing in a UX designer—when it’s needed.
Build smarter software that gets
better as you use it.
The future is pocket-sized.
Get access to the software you
need on your phone.
Integrated systes that collect crucial
data. And know how to put it to