Everything starts with a video call rather than a phone slot, so we can look at
the same screen. If you already have your Gemfile.lock to hand, mention it and
we will read it before we speak, which makes the first conversation specific
instead of general.
Or send the details below and we will come back to you.
Before we speak
Two things make a first conversation useful. Neither is a commitment.
Your Gemfile.lock. The single highest-information file in this
conversation. It carries your exact Rails and Ruby versions and every
dependency, which is what determines whether an upgrade is straightforward or
structural.
What your assessor or your customer actually said. The specific wording of a finding, a security questionnaire, or a blocked deal tells us which control you are being measured against, and that decides what the work has to produce.
What we will ask you
Which frameworks you are assessed against. What is forcing the date, and how firm it is. Who signs, and what they need to see. Whether the application has a staging environment, continuous integration, and a test suite you would trust to catch a regression.
What happens next
A video call, then a short written scope. The agreement is with Reid Morrison Inc., a Florida corporation, and it is corp-to-corp: an NDA before anything is shared if you need one, liability capped at fees paid, and your own security addendum signed.
How your code, your access and your credentials are handled is set out in full on our security page, which is written for the reviewer your CISO forwards it to.