Everything starts with a video call rather than a phone slot, so we can look at the same screen. Tell us which problem brings you here and what is forcing the date, and the first conversation is about your system instead of a generic pitch.
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.
The artifact that describes the problem. For software past its end of life,
your Gemfile.lock: it carries your exact Rails and Ruby versions and every
dependency, which is what determines whether an upgrade is straightforward or
structural. For a performance problem, a screenshot from your monitoring of the
moment it hurt. For AI tooling, which tools and plans your team holds.
What is forcing the date, in the words of whoever set it. The wording of an audit finding, a security questionnaire, a blocked deal, a service level or a board request tells us what the work has to produce.
What we will ask you
What is forcing the date, and how firm it is. Who signs, and what they need to see. Which frameworks you are assessed against, if any. Whether the application has a staging environment, continuous integration, monitoring, 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.
Our W-9 is available on request. It is in the legal name above and carries the EIN; neither is published, because a taxpayer identification number belongs in your vendor file rather than in a search index.