Frequently Asked Questions
Can’t find the answer you’re looking for?
Do you sell other services beyond the Technology Review Report?
Yes, along with the Technology Review Report, Rackless, Inc. also sells fractional Chief Information Officer, Chief Technology Officer, help desk support, and software development services. Micky's Technology Review Report is where most of Rackless' client relationships begin. If after writing and reviewing the report, Micky, the Rackless team, and our report clients can review whether there may be a good fit between Rackless and their company. If such a relationship seems feasible, Rackless can then work to help our report clients implement the findings from the report.
When counting our team members, who should we include in the count?
We recommend counting anyone as a team member if they are provided an email address or a phone number by your company. You would include both full-time and part-time employees, contractors, and more that have a corporate email address or phone number.
To get even more specific, you may use the Full-Time Equivalent (FTE) method. A company generally considers an FTE to be valued at 2,080 hours. For example, if you have 5 individuals that have been provided a corporate email account or phone number but 2 work part-time at 20 hours/week each, then your team has 4 FTE team members.
What is the preferred communication process for the report?
To keep costs as low as possible, we focus on efficiency in both communications and our work. At the core of our work is asynchronous communications powered by Rackless.app. Asynchronous communication is any type of communication where one person provides information, and then there is a time lag before the recipients take in the information and offer their responses. This asynchronous communication preference is why we have invested heavily in building and deploying Rackless.app.
At Rackless, we have found asynchronous communication improves the quality of the questions, requests, and responses. Why? Asynchronous communication allows recipients time to gather their thoughts, investigate multiple options, formulate opinions, document findings, and present their recommendations. To meet the demands of an increasingly connected and global workforce with varying, flexible, and offsetting work schedules, asynchronous communications become more popular than the more stringent synchronous option like meetings or calls. Our team members and clients often submit tickets during their work shift to come back the next day to find the ticket completed while they were off and even sleeping.
A bonus offered by asynchronous communications comes from the result: 100% documentation. Future team members can go back and review tickets to see what decisions were made and gain broader knowledge of the work completed and the motivation behind decisions. Before asychronous communications, this organizational memory was loss because calls and meetings were not recorded. Even if the call or meeting was recorded, many just don't have the time to wade through the formalities, small talk, and pleasantries of meetigns and calls to glean the nuggets of wisdom held in the recordings.
We understand that communication preference differ based on a company's geographic location (San Francisco v. New York) and also by age demographic (Generation Z v. Baby Boomer). As a result of these differences, we offer online web conference calls and onsite visits (aka synchronous communications) upon request to complement our asynchronous communications.
Is there a limit in the number of participants you will interview for the report?
No, there is no hard limit. Ideally, we want each department in your company represented as well as each level within management. If you have an employee, business owner, shareholder, or stakeholder that uses your technology today and you feel we would benefit from hearing their feedback, we are all ears.
Do we have to sign a contract for the report?
To keep costs as low as possible, there are no contracts to sign to purchase a Technology Review Report. This helps lower legal fees and thus keeps our report price to a minimum. If within 30 days of receiving your final report you are not 100% satisfied, we will give you a full refund, no questions asked (and no lawyers required😎).
Micky's daughter Amelia asked him what they were going to do after Post.Bid.Ship.? Sitting in a large retail store parking lot, Micky pointed to the rack of shopping carts. He said "One day Amelia, we won't need those shopping carts or those shopping car racks. The products those carts carry today will in the future be sold online and delivered to us."
Having just learned about prefixes and suffixes in elementary school class that day, Amelia said "So the store will be Rackless?" pointing to the rack that held the carts. Micky said 'Yes, exactly.' He went on to share with her that not only would the store need less shopping carts and less shopping car racks, but company's like Post.Bid.Ship. would no longer need physical servers and the racks that hold them due to the cloud.
The next day after Layla, Micky's wife gave birth to their twins Olivia and Crockett, Micky searched online to see if Rackless.com was registered. It was but not being used. MIcky that afternoon shortly after meeting his twins for the first time negotiated the purchase of Rackless.com. Why? A company wanting to hire Micky to build their help desk and recruit software developers needed to write a check to him to get started. What other name to use other than the one Amelia invented and that would be acquired on Olivia and Crockett's birth date making it extra special and marking the transition of Micky from building Post.Bid.Ship. to building Rackless.
How rare is one person that can be both the Chief Information and Technology Officer?
Micky having served as both Chief Information and Chief Technology Officers for multiple organizations makes him something of a unicorn. It is rare that one person has the skillset and experience to both buy and build technology.
To serve as the Chief Information Officer, a person must have mastered the skill of working with different departments and coordinating the purchase and deployment of Information Technology systems. To serve as the Chief Technology Officer, a person must have mastered the skill of recruiting and working with product owners, software developers, scrum masters, business owners, and multiple stakeholders to take a custom software development product from idea to the marketplace.
When you combine this with the fact Micky holds an MBA in Entrepreneurship from The University of Arizona, studied Venture Capital at the University of California, Berkeley, and has raised both Angel and Venture Capital for two startups both having experienced successful exits, his skillset and experience is definitely unique.
What countries, states, and cities do you currently serve as CIO/CTO?
We are currently serving clients in the following areas:
- Cleveland, Ohio
- Dallas, Texas
- Denver, Colorado
- Nashville, Tennessee
- Sioux Falls, South Dakota
If you live outside these areas, contact us
because we are expanding to new areas across North America.
What is the timeline for the Technology Review Report?
Ideally, the goal for us and your team will be that we work to have the final report submitted within 90 days of purchase. To make that goal happen, we need to be timely in responding to tickets, request for interviews, and more. Here is how the timeline breaks down and how we envision the report being written.
First, we will conduct all interviews of key personnel within the first 30 days of purchase. These interviews may take the form of tickets submitted via Rackless.app with questions that interviewees can respond to via written or recorded answers. These interviews may also occur via Zoom recorded meetings plus potential onsite visits as time, budget, and logistics allow.
Next, our goal will be to write up our initial draft of the report within the first 60 days. This initial draft will include our first impressions written into the start of our six (6) main sections: Executive Summary, About the Authors, About the Participants, Best Practices, Competitive Landscape, and Recommendations.
Between day 45 and 60, our goal is that you and your team will have the opportunity to ask follow-up questions and input from the draft helping us refine the report into a final version by day 90. All of this will be done with the goal that on day 90 if not before, the final report will have be submitted.