Write a Review
Verified Profile
Level 12 brings an expert perspective to companies who need well-crafted, lasting solutions to their data and software challenges. We do this through invested partnerships, proven processes and frank, honest communication.
Leading software development service providers in Louisville, KY. We Specialize in building web applications, Robotic Process Automation, databases, data and reporting solutions, dashboards, integration, web portals. Located in the greater Louisville, KY area.
Locations
United States
326 E Court Ave,
Jeffersonville,
Indiana
47130
812.285.8766
Focus Areas
Service Focus
- Software Development
- Robotic Process Automation
- Artificial Intelligence
- Mobile App Development
- Cloud Computing Services
Client Focus
- Large Business
- Medium Business
- Small Business
Industry Focus
- Financial & Payments
- Transportation & Logistics
- Healthcare & Medical
Level 12 Executive Interview
Royce Hall
Director of Business Development
Kindly share your feedback on how GoodFirms has been doing so far in increasing your visibility among potential clients.
GoodFirms has been a great resource for Level 12 so far. They make it easy to get client feedback and have already increased the number of potential clients going to our website. The platform is easy to use, and the GoodFirms team is very responsive to my needs.
Please introduce your company and give a brief about your role within the company?
Level 12 is a full-service software development shop. We help businesses design and build vital software assets to handle complex data problems, automate repetitive processes, and bring new products to life.
I am the Director of Business Development at Level 12 and help business leaders figure out if custom software is the right fit for them and what those software products should look like.
I am the Director of Business Development at Level 12 and help business leaders figure out if custom software is the right fit for them and what those software products should look like.
What was the idea behind starting this organization?
Level 12 is built upon two core principles: Quality software development, and Client Empathy.
We started at Level 12 because we are passionate about building good software. There are lots of software developers and development shops out there. Still, many are more focused on making money than taking the time to build high quality, well-tested software. We want to change that.
As passionate as we are about code quality, we are equally dedicated to Client Empathy – truly understanding our client's business needs so that as consultants we can give them the right advice, even if that advice is "custom software is not the right move for you." We pursue the betterment of our clients, not just a paycheck. We dig at our client's problem until we can own it and feel the rub that our client feels, and then tailor solutions to conquer those problems in an Agile fashion (delivering early and often).
We started at Level 12 because we are passionate about building good software. There are lots of software developers and development shops out there. Still, many are more focused on making money than taking the time to build high quality, well-tested software. We want to change that.
As passionate as we are about code quality, we are equally dedicated to Client Empathy – truly understanding our client's business needs so that as consultants we can give them the right advice, even if that advice is "custom software is not the right move for you." We pursue the betterment of our clients, not just a paycheck. We dig at our client's problem until we can own it and feel the rub that our client feels, and then tailor solutions to conquer those problems in an Agile fashion (delivering early and often).
What are your company's business model–in house team or third party vendors/ outsourcing?
We are a small (think concentrated) in-house, on-shore development team. We hire developers who understand how to write high-quality code and how to consult with clients to reveal the best solutions. Our hiring process is designed to find the truly "gifted" developers to add to our software "special forces" team.
How is your business model beneficial from a value addition perspective to the clients compared to other companies' models?
We are both consultants and software engineers. Our value add is that we help our clients see the more foundational issues in the opportunities and problems they are trying to address with software. Many companies will jump right in and start writing code – but if they are not solving the right problems, even the best quality code will end in project failure. Practicing Client Empathy helps us avoid the most significant risk in software development – building the wrong thing. So from the very beginning of our engagements, even in the sales process, we help our clients and potential clients see at a deeper level what issues they are facing and uncover opportunities and questions they had not previously considered. We also provide project validation and engineering phases where we document for our clients what software solutions they need and even offer wireframe mockups that they can either pursue with other development teams or with us. It is hard for larger firms to do this well as they tend to hire faster with less emphasis on Client Empathy. As we like to say, we do not just code monkeys.
What industries do you generally cater to? Are your customers repetitive? If yes, what ratio of clients has been repetitive to you?
We are capable of servicing almost every industry. Our most substantial clients have been in Fintech (Payment Processing/Merhcant Services in particular), Transportation/Logistics, Green Energy, Manufacturing, and Healthcare.
Nearly 100% of our clients are repeat clients.
Nearly 100% of our clients are repeat clients.
Mention the objectives or the parameters critical in determining the time frame of developing a mobile app.
There are a few big questions we have to ask before setting the scope and timeline of a mobile app project.
First, do you even need a mobile app? Many people want a mobile app because that is what we think of when we say "app," and it is refreshing to have something on the Google or Mac store. What people don't realize is that you have to start with a web app, then build out the mobile app for either Droid or Mac. If you want the app on both stores, you are building the project 3 times. Is this necessary? What is the demand for the app currently? How long will it take to pay back this investment? Would having a mobile-friendly web app that has an icon on your phone/device suit your needs (for 1/2 the cost)?
Second, you have to ask what features are necessary. We made a video where we compare making a tank to making a milk truck (posted on our GoodFirms profile) that explains this pretty well. Often people come to us with a scope of work that amounts to a tank. But when we start asking, "do you actually need the treads and armour," it turns out that a lot of those feature requests people just thought sounded cool. We have to ask, what is the most important feature - if you only had "x" this project would be a success. Let's start building that, and as we get user feedback, make additional features, so we end up with something that meets the user's needs exactly. You thought you needed a tank, but when the project is over, you end up with a milk truck that meets your real needs.
Once we have figured out what are the essential parts of the project, then we can start to define timelines.
First, do you even need a mobile app? Many people want a mobile app because that is what we think of when we say "app," and it is refreshing to have something on the Google or Mac store. What people don't realize is that you have to start with a web app, then build out the mobile app for either Droid or Mac. If you want the app on both stores, you are building the project 3 times. Is this necessary? What is the demand for the app currently? How long will it take to pay back this investment? Would having a mobile-friendly web app that has an icon on your phone/device suit your needs (for 1/2 the cost)?
Second, you have to ask what features are necessary. We made a video where we compare making a tank to making a milk truck (posted on our GoodFirms profile) that explains this pretty well. Often people come to us with a scope of work that amounts to a tank. But when we start asking, "do you actually need the treads and armour," it turns out that a lot of those feature requests people just thought sounded cool. We have to ask, what is the most important feature - if you only had "x" this project would be a success. Let's start building that, and as we get user feedback, make additional features, so we end up with something that meets the user's needs exactly. You thought you needed a tank, but when the project is over, you end up with a milk truck that meets your real needs.
Once we have figured out what are the essential parts of the project, then we can start to define timelines.
How much effort in terms of time goes into developing the front end and back end of a mobile app?
A lot of the applications we build are for internal use, so our work tends to be more on the backend and database side of things. If the backend doesn't function well for these apps, having a nicer UI/UX is not going to be of much value. To truly answer this question, though, we would have to go back to Client Empathy – what is most famous for the client. Is the project a UI/UX update, then we will spend most of the time on the front end. Is the project automating bookkeeping and accounting, then it is going to be mostly backend work. It all depends on the needs of the client.
What are the key parameters to be considered before selecting the right platform for a mobile application?
What are your key objectives? What is your target audience? What devices do they use? We tailor our solutions to the needs of our clients, so there is no right or wrong platform per se. We are platform agnostic. We look at each opportunity on its own merit and guide our clients towards the solution that makes the most sense for them (even if that doesn't include us).
Which platform do you suggest your clients, to begin with when they approach you with an idea (Android or iOS) and why?
Most of the time, we start by asking if a mobile app is going to serve their needs. Many projects can be executed just as well at a fraction of the cost with a web app. Especially if you are operating on a "build it and they will come" mentality, it can pay big dividends to start small and prove the concept before biting of the expense of building a mobile app (which has to start some web app development anyway). If we are building a mobile app, we have to ask what is going to serve the client's users the best. Are they mostly Droid or iOS users? If it is an internal app to the business, what devices do you stock your employees with? Asking the right questions about key functionality (and budget) helps guide us to which platform is appropriate for the project.
Android or iOS, Native or Hybrid — which platform is best to use to build your app? What are your recommendations?
There is no right or wrong answer, it all depends on the need of the clients. If the majority of their users are Mac users, then iOS may make more sense. If they are droid users, that may make more sense. Many of our projects end up being hybrid web apps because this approach gives you much bang for your buck. It is a lower cost of entry than doing a mobile app from the start, especially if you are trying to prove an idea for the first time and don't have a subscriber client list yet.
What are the key factors that you consider before deciding the cost of a mobile application?
The key factor is what features the client needs. The more features, and the more platforms the client wants to be on, the more coding work and complexity are added to the project. Complexity plays a large role in the price estimation as well. Complexity adds to price exponentially, not logarithmically. The more complex a project is the more potential for unforeseeable hurdles that not only take much time but a lot of skill and thought to resolve. We often start simple, with an MVP that we can deliver quickly and will provide the essential functions of the app, then we build out additional features in an iterative fashion.
What kind of payment structure do you follow to bill your clients? Is it Pay per Feature, Fixed Cost, Pay per Milestone (could be in phases, months, versions etc.)
We try to keep payment easy and reasonable to our clients by billing for time and materials. Software is fundamentally a discovery process, so it is tough from the start of a project to define exactly what the scope (and therefore price) will be. Our clients often get into a project and say, "our business needs have changed, and we need "xyz" now." Billing by the hour allows us to adjust quickly without getting into price and contract wars with our clients. Fixed cost contracts structurally put us at odd with our clients – we would get more profit by blasting through work with less emphasis on quality or concern for the evolving needs of the client. Billing by the hour allows us to adapt to the actual needs of our clients.
Do you take in projects which meet your basic budget requirement? If yes, what is the minimum requirement? If no, on what minimum budget you have worked for?
We are pretty flexible. Typically our projects are between $20k and $250k, although we have done larger and smaller.
What is the price range (min and max) of the projects that you catered to in 2019?
Our smallest project in 2019 was about $2k documenting an API (this was a loss-leader project). On the high side, we had a couple of projects around the $250k mark.
Which business model do you suggest to your clients, enabling them to generate revenue from mobile applications? Why?
It depends on the needs and vision of the client. We have built a couple of SaaS products that have a tiered monthly subscription model. Another client is going to use the app we built to sell franchises. Another uses our app for wagering and doesn't need a subscription service. Our advice and software tailoring is all dependent on the needs of the client.
Level 12 Clients & Portfolios
Level 12 Reviews
2 Reviews
- All Services
- Mobile App Development
- Relevance
- Most Recent
- Rating: high to low
- Rating: low to high
Sarah Gerald, CPP, Director of Business Technology at Merchant Solutions
Posted on Mar 13, 2020
Excellent choice for your software solution
Review Summary
Level 12 is always my number one choice for Software and development solutions. Randy and his team not only put together some of the best custom tools for business use, they also grasp the true set of requirements that a client may need, which is one of the most difficult processes on new development. Most 3rd Party developers require a client inhouse technical BA to enhance the message between a business user (client) and the developers at a 3rd party organization. Not at Level 12. Level 12 is a simple one stop shop and Randy's team will always pull business users through the experience and the user cases that the client has ultimately asked for. I've used Level 12 for several large tools in the Acquiring Payment space in which they build from scratched, maintained for the ongoing development and supported us for a long standing relationship. An additional note, if you're also looking for API development, this is your team! You will not be disappointed regardless of what your Software needs are or what your business segment may require.
What service was provided as part of the project?
Mobile App Development, Web Development, DevOps
Jonathan Erwin, CEO at Red E App
Posted on Mar 12, 2020
Everything is working great!
Review Summary
What was the project name that you have worked with Level 12?
Red E App
What service was provided as part of the project?
Mobile App Development, Software Development