Process makes perfect
Trusted IT partners with over 200 founders and leaders from billion-dollar brands to innovative startups worldwide. The last dull day we had was a decade ago.
Top app development company
Who are we?
Who is O2SOFT?
O2SOFT, a bespoke software development firm based in London, was founded in 2011. We had restricted capabilities at the time of the launch and could only create standalone mobile and web apps. Our procedures were poor, and we made several errors when breaking ground. We ate all of the costs until the projects were re-started, a series of strategic actions that earned our clients' trust.
We introduced strategic management processes into our organization in 2013 and pivoted our organization to develop integrated, business-first solutions that were a byproduct of mobile and web technologies coming together and working seamlessly to provide a lavish experience, learning quickly from our mistakes. While our solutions looked and felt nice, the customized functionality they provided to the client organization allowed the client to place a high level of reliance on the solutions, as well as on us as an IT partner.
At O2SOFT, we believe in doing things correctly the first time. Over 200 real-world business issues have been solved, and hundreds of creative ideas have been realised, thanks to our collaboration with executives and founders from billion-dollar corporations to inventive startups. Our solutions are designed to handle and age well, are optimised for end-user interaction, and may be used in conjunction with or in addition to the current IT environment. We continue to service clientele with whom we originally worked years ago, among others.
What services does O2SOFT provide?
Strategy - helping you figure out "what exactly should I build?"
Design - the process of creating aesthetically appealing, simple-to-use interfaces that delight your customers and make your company seem good.
Development - the process of developing and testing code that works smoothly, gets the job done, and is dependable on a daily basis.
Quality assurance (QA) is the process of ensuring that we always produce the correct item and that it works properly across many platforms.
Deployment and DevOps – delivering your product as fast as possible to your consumers.
Hosting and monitoring – ensuring that everything works properly and safely once it's deployed.
Ongoing Support – With your own dedicated, fractional product crew, keep your product in top shape and respond quickly to your requests.
Your strengths and weaknesses?
We aggressively seek out the finest solution and manage projects from start to finish. Our company's reputation has been built on timely delivery and precise solutions.
The following kind of partnerships or relationships fit us best:
New development - "from idea to MVP" or "from MVP to version 1" o Dedicated software team - a section of a software department o Takeover and improvements of legacy software
Boosting existing teams – Adding common values to present teams o Turnarounds or project rescues
Provide remote bodies to organizations in order for them to fill seats
We do not engage in the following activities:
Assign our staff to work with our clients on-site.
Contract-to-hire engagements — this, too, should be handled through a staffing agency.
- New development - "from idea to MVP" or "from MVP to version 1" o Dedicated software team - a section of a software department o Takeover and improvements of legacy software
- Boosting existing teams – Adding common values to present teams o Turnarounds or project rescues
- Provide remote bodies to organizations in order for them to fill seats
- Assign our staff to work with our clients on-site.
- Contract-to-hire engagements — this, too, should be handled through a staffing agency.
Our composition and constitution
We are a group of 40 highly competent professionals who have all gone through a rigorous selection procedure to join their colleagues at O2SOFT.
Are you able to provide Continuing Professional Development?
For the time they spend learning and contributing, all of our workers get rewarded. Reading relevant literature, attending industry conferences, and participating in and presenting at local meetings are all part of this process.
We have frequent lunch & learn events in the office so that our workers may learn from one another. We also cover the cost of any Scrum, project management, engineering principles and practices, great design, or business strategy training programs that an employee may take at any time.
Hours typically worked per week?
Our employees typically charge between 35 and 40 hours per week.
Where are your offices?
Our registered offices are in London and Wisconsin, respectively. In Pakistan, India, and Singapore, we also operate support centers.
What is your hiring process?
There are three phases to our screening process:
Technical Phone Interview
- Phone Interview with the most relevant individual
Coding Test - This eliminates about 80% of all candidates.
- References in-person interview
When we hire developers, we look for people who:
- would programme even if it weren't their job,
can quickly acquire and apply new, even alien, concepts under pressure, and
have a strong grasp of computer science fundamentals.
Of course, different people have different hobbies. Each individual develops their unique "T-shaped" competence in one subject over time (ex: security or front-end or SQL optimization). As a result, our whole team is fluent in a variety of languages, technology stacks, and specialties.
Can you provide resumes for my project?
Unless it's for an official security clearance, we don't do this. When we ask for resumes from team members, it's a dead giveaway that our potential customer prefers a staffing arrangement. This is something we want to avoid, as previously stated. You may rest assured that you will interact with a variety of team members before we start working on your project. We're probably not a good fit for you if you're not excited about your team before we start working together.
Our Sales Process
Purpose of the first call?
To make sure we're a good fit, we always start with a phone call. We seek for a fair budget, a clear vision and direction, and total devotion to the project.
Do we have any references?
Absolutely. In our opinion, checking references is an important part of the buying process. We'll usually give references when we've decided that we're a good fit for you and your project.
Will you sign our NDA?
We will not sign an NDA before our first call. We must have a thorough understanding of the industry in order to assess whether there is a possible conflict with current or past clients. Every year, we talk with approximately 500 potential new clients. It is inescapable that we will have similar ideas.
Only if the following criteria are satisfied will we sign an NDA:
It is reciprocal or bilateral in nature (we typically use ours)
We understand the project's requirements and believe that the project and customer are a good fit for O2SOFT.
We are not in violation of any other commercial agreements.
Will we participate in an RFP?
In a nutshell, it's not likely. We've written a full blog article about why, but here's a brief summary:
RFP requirements are usually quite specific, yet they are frequently devoid of any business context.
There is a tiny probability that this document will have the best feature set. We place our confidence in someone else's ability to correctly capture the criteria when we agree to respond to an RFP. By doing user interviews, mockups, prototyping, releasing actual software, and collecting feedback from real users, the project team may learn more about the proper features. This contract model sets the customer and consultant against each other from the outset.
Are you comfortable with fixed-bids?
As you may have guessed, we don't accept fixed-bid offers. We politely decline RFPs and utilize the opportunity to educate the potential customer on why RFPs aren't a good fit for custom software projects.
Can O2SOFT take over an existing project?
Absolutely. We always start with a live system presentation, followed by a code audit. When we conclude the audit, we provide you a detailed report that includes an analysis, recommendations, and a takeover proposal (if applicable).
What are your privacy and IP policies?
Who owns O2SOFT's code and designs developed throughout the project? You certainly do. Before we start working, we'll draw up a services agreement that provides you ownership of all work products and deliverables as long as we're paid for the services we offer.
Not ready for development yet. Help?
When customers come to us, they are almost never ready for development. It's critical that we spend the time up front to assist you figure out what you should create and how much money you should set aside for your project. Find out more about our pre-project consultation service.
What are the steps involved in the creation of Custom Software?
If you require new software, we'll use our pre-project consulting technique to help you measure up your project before moving forward with a Discovery, Design, and Planning engagement. We'll begin working on your software after DDP. From beginning to end, you'll be a part of the process.
Here's where you can learn more about our procedure.
Are you taking on new projects? What’s the timeline to get started?
Yes, we are always evaluating new projects. It takes around two weeks to complete the pre-project consulting procedure. The Discovery, Design, and Planning phases take 4-6 weeks to complete. Then comes the development phase.
What’s the usual team size?
Typically, each project team comprises of two to three developers. Each project team is assisted by UI/UX designers, software testers, managers, and cloud engineers. Because each development team shares support resources, we can decrease project costs for clients. We may also increase developer productivity by ensuring that they spend their time working on production-level code rather than doing other things.
What are the usual roles on the team?
Each team has a Project Lead, a full-time developer who is in charge of facilitating communication and planning with the client and among team members.
How does O2SOFT communicate?
Interactions with the Project Lead aren't the only way for project teams and customers to communicate. Every employee at O2SOFT has the power to communicate with our clients. During the work week, O2SOFT staff and their clients often exchange phone calls and emails.
Each project team at O2SOFT has its own email address (for instance, [email protected]). All formal communication strategies that will be utilized during the project are listed below:
Weekly Status Update
Outline the following: what was accomplished last
week, what will be accomplished this week, any
queries or concerns, and the project's current
This should be a weekly call that is established at the beginning of the season. The aim is to check in and talk about any issues, get answers to questions, follow up on action items, or get feedback.
The Team Lead or PM will send an email to the customer outlining what has transpired since the last build and what is available for testing and feedback.
- Outline the following: what was accomplished last week, what will be accomplished this week, any queries or concerns, and the project's current state.
- This should be a weekly call that is established at the beginning of the season. The aim is to check in and talk about any issues, get answers to questions, follow up on action items, or get feedback.
- The Team Lead or PM will send an email to the customer outlining what has transpired since the last build and what is available for testing and feedback.
How do you manage projects at O2SOFT?
Lack of communication is one of the most prevalent causes of project failure. Establishing communication and planning routines is the most important aspect of software project management. Here are a few examples of rhythms:
A weekly meeting of one hour to review achievements, failures, and future goals
Team members demonstrate what they accomplished the previous week.
Everyone discusses how the project's processes/techniques may be improved.
A weekly timetable has been established.
- A 15-minute daily standup is required to maintain team momentum.
Our project management processes are built on the principle of "no surprises," which guarantees that everyone is kept informed at all times and that risks are addressed as they occur.
- Team members demonstrate what they accomplished the previous week.
- Everyone discusses how the project's processes/techniques may be improved.
- A weekly timetable has been established.