Frequently Asked Questions
How can we help you?
-
How much does an engagement costs?
We charge a fraction of what it costs to do it in-house and deliver it in half the time or faster. We practice agile development. We charge a flat fee per sprint but allow for scope changes (which are billed separately) at customer request.
-
When can we get started?
We can start as soon as you sign our Statement of Work. Typically we see this process take 2-3 weeks from the first introductory call to the start of our engagement. We can have this call at anytime, so please make sure that you schedule it today. After talking with you and assessing if we're a proper fit, we'll execute a Mutual NDA and then send over an Engagement Workbook so we can gather all the requirements for your project and estimate the cost.
-
How can we expand the scope of work?
We can easily add additional sprints to a Statement of Work. We will agree on what goes into a Sprint, which will determine the number of Sprints required.
-
How long does an engagement last?
Our typical engagement model begins with a complete platform rollout. This includes roughly 6-8 sprints, each 2 weeks in duration. During this time we set up all AWS Accounts with IAM federation, Cloud Trail audit logs, a comprehensive release engineering process, total observability with our Site Reliability Engineering sprint, Remote Access Management, GitOps Operations by Merge Requests. The first engagement takes roughly 3-4 months to complete. These engagements have extremely well-defined project plans. Ask us and we can show you how this looks like.
-
Do we provide ongoing support?
We provide entirely (optional) support for customers. By in large, most of our customers take over the day to day management of their infrastructure. We're here to help out anywhere you need us.