FAQ

The following are some more details related to IWebSquare’s background and ownership.

iWebSquare’s CEO, Umang Patel, is the owner of 100% of the firm and is actively engaged in the day-to-day operations and managing of IWebSquare. Umang’s leadership style puts a priority on (1) assisting people who serve our clients and (2) developing trust with every interaction.

The following are some more details related to IWebSquare’s background and ownership.

iWebSquare’s CEO, Umang Patel, is the owner of 100% of the firm and is actively engaged in the day-to-day operations and managing of IWebSquare. Umang’s leadership style puts a priority on (1) assisting people who serve our clients and (2) developing trust with every interaction.

• Non-technical entrepreneurs or important individuals with titles such as CEO, COO, President, Director of Operations, or at times Director of Technology or CTO
• Technology-frustrated businesses – outgrown their current systems/process or need to enhance what they already have in their organization
• Mainly service-based companies that view custom software as a competitive advantage
• Established small and mid-sized businesses with about 10 to 800 employees

• The average IWebSquare customer has been doing business with our company for 5+ years, on a continuous basis.
• Since 2001, we’ve gained more than $600M in measurable ROI for our clientele, either as new revenue or improved performance.
• We’ve worked alongside 350+ companies and carried out over 500 projects.
• 98% of our customers come back for a second engagement.

• Everyone is direct in their communication, possess complete independence over their time, and management keeps full financial transparency always.
• People participate in organization activities (like our quarterly wellness adventures or Game and Group Activities), and many people hang out socially.

• Assisting our clients to attain their 100 % potential, however, they determine good results.
• Providing students with the real-world experience they wouldn’t usually get.
• Setting up a place of work and culture that assists people’s personal goals.

• We care about the progress of IWebSquare and our clients (regardless of their size).
• We motivate others with our desire for excellence.
• Our enthusiasm to see others do well means we choose to go “above and beyond” to assist our colleagues and customers without the need of ever being asked.
• We have the long-term view when looking for possible outcomes with our customers and peers.

• We re-conceptualize problems to uncover practical, beneficial solutions to difficult challenges.
• We discover underlying causes and get beyond solving the signs and symptoms.
• We wisely distinguish what should be done well now, and what could be enhanced later.
• We take on significant challenges, along with day-to-day improvements, with the same passion.
• We take informed risks and aren’t reluctant to champion fresh (at times unpopular) ideas.
• We figure out good judgment to help make smart decisions regardless of ambiguity.
• We challenge existing assumptions when justified, and recommend more effective approaches.
• We keep our customers nimble by reducing complexity and using the time to streamline.

• We listen carefully rather than responding quickly, so we're able to understand.
• We’re known for honesty and directness, even when your ideas are controversial.
• We quickly accept mistakes.
• We retain trust even if formal relationships end.
• We always keep going and carry out everything we say we'll do.
• We depend on our colleagues to carry out the right things.
• We display consistently good performance so colleagues could depend on us.

• Strategy - assisting you to answer the question, “what precisely do I need to build?”
• Design - developing attractive, easy-to-use interfaces that excite your users and make your organization stand out.
• Development - writing and testing code which works smoothly, will get the job done and is dependable day after day.
• Quality Assurance - making sure we’re always constructing what's right, and it functions securely across numerous platforms.
• Deployment & DevOps - getting your company's product to your people with minimum difficulty.
• Hosting & Monitoring - continuing to keep things running efficiently and securely after its deployment.
• Ongoing Support - maintain your product in good shape and responding to your requirements promptly with the help of your own committed, fractional software team.

• Development of new product - “idea to MVP” or “MVP to version 1.”
• Dedicated software team - fractional software department
• Legacy takeover and remodels
• Project rescues or turnarounds
• Boosting current teams - enhancing current groups with shared values

• Build-to-spec
• Only development or just QA - with our company, we bring the entire team, so it’s all or nothing
• Place our people on-site with our company's customers
• Offer warm bodies for businesses to fill seats - get a staffing company for this
• Contract-to-hire engagements - again, get a staffing company to do this

Until now, we've got over 150 people committed to client projects.

All of our people get paid to gain knowledge and share. This approach consists of reading relevant books, visiting industry conferences, participating and speaking at local meetups.

We frequently keep lunch 'n learns at the office so our people can gain knowledge from one another. Additionally, we pay for each employee, at any time, to participate in training courses on Scrum, project management, engineering best practices, great design, and business strategy.

Our full-time people bill an average of 35-40 hours of their time each week.

IWebSquare gets over 2,000 new applicants per month.

Our vetting process consists of 6 steps:

1. Application Review
2. Online Test
3. HR Interview and Reference Check
4. Written Test
5. Technical Interview
6. Square Staff Match

We’ve interviewed over 250,000 candidates to discover the team of people we work together with today.

Usually, different people have diverse interests. With time, each person becomes “T-shaped,” building their particular specialty in a single area (ex: security or front-end or SQL optimization). As a result, collectively, our team is fluent in numerous languages, technology stacks, and specializations.

This action isn't something we carry out unless it’s to have an official security clearance. Whenever prospective clients request resumes of the staff, this can be a red flag that our potential customer would want a staffing relationship. As stated before, it is something we strive to avoid. Be assured; you’ll have interactions with several team members before we start work on your company's project. If you’re not enthusiastic about your team before we start work, then we’re probably not a great fit for you.

We always do an initial call to make sure that we’re a great fit. Things we check for are an accountable budget, a clear vision and direction, and a 100 % dedication to the project.

Yes, sure. We feel checking references is an integral part of the purchasing process. We generally send over references once we establish that we’re an excellent fit for you as well as your project.

We won't sign an NDA before our initial call. It’s essential that we understand enough regarding the business to gauge whether there’s a conflict with our existing or past customers. Additionally, we speak to over 500 prospective new clients each year. It’s inevitable that we hear the same ideas.

We'll only sign an NDA if:

1. It’s mutual or bilateral (we typically utilize ours)
2. We fully grasp the needs of the project and feel that the project and client are an excellent match for IWebSquare
3. We aren't violating any other agreements that we've got as an organization

Short answer - probably not.

• The needs in RFPs are usually really detailed but generally, fall short on business context.
• The possibility of this document containing the ideal set of features is quite low.
• If we agree to respond to an RFP, we depend 100% on somebody else’s capability to find the right requirements. The project team better learns the right characteristics via user interviews, mockups, prototyping, releasing actual software, and receiving feedback from real users.
• This contract style leads to the client and consultant working against each other right from the beginning.

You may have figured out; we do not carry out fixed-bid proposals. If prospective clients approach us with RFPs, we politely decline and utilize that interaction as an opportunity to inform the potential client about why RFPs aren't an excellent match for custom software projects.

Definitely. We always begin with a live demo of the system and after that a code audit. After we complete the Audit, we give you a complete report that consists of analysis, recommendations, Proposal for takeover (if applicable).

Who is the owner of the code and designs IWebSquare creates during the project? You do. Before starting our work, we’ll put a services agreement in order which will allocate ownership of all work product, and deliverables to you provided that we get paid for the services we carry out.

Most customers are never ready for development when they get to us. It’s essential that we take some time upfront to assist you to figure out what's right to build and a sensible budget for your project.

If new software - we’ll work together with you through our pre-project consulting process to size up your company's project and then proceed with a Discovery, Design & Planning engagement. After, we’ll begin the process of development of your software. You’ll be engaged each step of the way.

Yes, we're always assessing new projects. The pre-project consulting process takes ~2 weeks. Then, our Research, Design & Planning phase requires 4-6 weeks. Following that, development commences.

The common size for every project group is 2-3 developers. Every project group is supported by UI/UX designers, software program testers, managers, and cloud engineers. Allowing us to be in a position to decrease project expenses for customers. We’re also in a position to make developers much more effective by making certain they invest their time writing production-level code, not messing with other tasks.

Each team is designated a Project Lead, a full-time developer on the team who has extra responsibilities for assisting communication as well as planning with the client and between the Team.

Each team gets a Project Lead, a full-time developer on the team who has additional duties for facilitating interaction and planning with the client and within the Team.

Projects are unsuccessful for one primary reason - poor communication. Setting up communication and planning rhythms is an essential component of software project management. These rhythms consist of:

• Weekly meeting to review successes, failures, and potential plans - 1 hour
• Team members demonstrate the things they completed the week prior
• Everyone talks about how they could enhance the processes techniques on the project
• A comprehensive plan for the upcoming week is agreed
• Daily standup to build team momentum - 15 minutes max

Our project management practices focus on a “no surprises” philosophy that will keep everybody informed all the time and attacks risks as they arise.

Short answer - Everybody. Every person on our teams is empowered to communicate with customers directly. These will keep things moving along and will help preserve our flat organization structure.

We want clients to be actively taking part in their projects. You will be the one getting the know-how regarding your business and industry to the table. Without that, we've no clue if we’re developing what's right. Involvement consists of weekly calls or meetings and availability through phone during regular business hours.

Client feedback is quite critical all through the process. You need to offer input always, even early-on if the functions are still rough. Your feedback can provide us context about what’s crucial to you and your business. This approach will help us focus on and stay tied to your requirements.

Yes. This sort of flexibility is vital and can ascertain the success of a project. However, significant changes following the kick-off may impact the budget or schedule.

Yes. We feel open, and transparent communication is the foundation of highly successful software projects. You’ll always learn what’s happening on your company's Project and you’ll be in regular contact with our team. It’s quite Normal for our Project Leads to call their customers many times a week. Additionally, we present weekly status updates and frequent releases on a staging site to keep you informed.

The software is hardly ever “done.” We understand that our customers and their users will continue to keep getting amazing ideas all through the process and after the initial delivery. As your business transforms, your software will have to advance and adapt.

It’s common following the first release to pause on developing capabilities for a bit and concentrate on improvements or fixes to push user adoption.

QA staff engages from the Day 1, and we create test plans at the start of projects. Testing occurs all through the project, not merely towards the end. Additionally, we exercise code reviews and pair programming to make sure that we write quality code always.

IWebSquare teams get amazing power from open source tools, libraries, frameworks and indeed complete projects or our specific proprietary libraries. We by no means redesign the wheel if there is a tool that's well suited for fixing a problem. We always code from scratch the pieces which make your company's project tailor-made and worthwhile.

Examples of common projects for our company can be:

• Code Review - 2 people, 1 week
• Research, Design & Planning involvement - 3 people, 4 weeks
• The idea to Version 1 - 3 people, 3 to 5 months
• Proof of Concept (PoC) - 2 people, 1 to 2 months
• Project Rescue - can vary as per project
• Dedicated Team - retainer each month
• Fill a gap till an internal team is appointed - 2 people, 3 months
• Staff enhancement with the current internal team - 3 people, 6 months

More often than not, we’ve completed projects for clients who've only enough budget for a “Version 1.” They invest some time getting acquainted with the software and return for one more round of design and development with a more knowledgeable sense of where the software must go.

We can’t answer this question responsibly till we know your company's idea, business, market, users, etc. Although we can’t precisely say what your company's project will cost, we can draw on the 500+ projects we’ve completed since 2001 and let you know what’s usual for the projects we’re most suitable to assist you for your requirement.

Even though it’s challenging to understand the precise costs of the project without undergoing a discovery phase such as our Research, Design, and Planning phase, we can usually assist you to fix a responsible budget before you decide ever to appoint us.

It’s also essential to consider that a majority of projects get split up into multiple phases. In the first phase of development, our objective is always to concentrate on the maximum value capabilities and architect something which positions us for future Phases.

Regardless of how small or large your company's budget is, it’s always our objective to provide value for our clients that substantially surpass the fees we charge.

A usual small team for the projects we handle is two to three full-time developers. A big Team is four to six people.

To get a rough approximation of project duration, we consider the estimates given above and divide it by 32 hours for each person on the team. For instance, a 1200-hour project requires approximately 3 months of calendar time for a Team of 3 people (1200 hours (3 people * 35 hours person week) 4 weeks month = ~ 4 months).

On huge projects, we’re in a position to add people and move quicker. That’s pretty incredible, in fact, and not something each team or company are capable of doing. Expanding the Team demands that we've got extra employees accessible.

For projects which have a total fixed budget, we keep track and bill on an hourly basis. We believe this can be the most straightforward approach to Billing. If somebody is away sick, then you don’t spend on their time. This approach also ensures that everybody (including clients) focus on the most useful capabilities at any given time instead of helping scope creep. It requires everyone’s understanding of the budget and the way we’re tracking to help keep the project on target.

For projects which have a total monthly budget, we continue to track hours to make sure that we strike the mark every month.

We do have standards and best practices set up that inspire each team to carry out their best to build up a high-quality product.

We stand behind all of our products and support all software bugs or glitches. If you come across a bug then we will fix it we don't charge for bugs, and you do not need to be on a maintenance plan for us to fix bugs.

When billing on an hourly basis, we invoice monthly in arrears. Ex: On February 1st, you’ll get an invoice for hours logged January 1st to 31st. Payment is due in 10 days.

When billing for a dedicated team, payment is due in advance for that month’s team. Ex: On February 1st, you’ll pay for February.

On a larger project, the payment is typically 50% down, on the start of the project, 25% on the Beta release of the software , and 25% on the Final release of the software.

Our rates differ with time, but we strive to maintain our blended rate between $50 hour to $60 hour.

Experience. The swiftness of delivery. Reputation. Demand. Talent. The all-around software market.

Yes. Our engagements are “fixed budget, scope controlled” which means we’ll assist you to build a responsible budget and we’ll stay with it. Since we’ve not ever worked alongside people who have got lesser number of ideas Than they have money or time, our responsibility would be to find out the ideal software application we could construct for the given budget. That needs in-depth knowledge of the users as well as the market. Following that, we’ll try to manage the scope of the project, both in depth (polish, refinement, sophistication) and breadth (characteristics, functionality).

We guarantee cost. In an industry that’s known for cost overruns as well as low-ball bids, we go to great lengths in our upfront process to de-risk projects. These initiatives result in spot-on solutions, precise estimates, and highly effective relationships. In case we underestimate something then we’ll take in 100% of the extra cost till we’re back to normal. Why? Because it’s the right thing to do.

Additionally, we guarantee that you'll be able to terminate anytime. By placing the power of termination within our clients’ hands, it assures we’re held accountable every single step of the way.

We brag a 96.5% success rate in a market where 42% is a norm. Communication, tight frequent feedback loops, and being lean have attributed to our high level of success and reputation of fast, spot-on solutions.

IWebSquare comes with a broad skill set that gives us the ability to understand more about options and choose the best languages, platforms, and tools for every job. We do roughly 80% of our company's work with these:

• Web - ASP.NET Core (C#), PHP, Node.js, ReactJS, AngularJS, HTML5, Bootstrap, Sass
• Mobile - iOS, Android, Cordova
• Desktop – Java, Microsoft WPF (C#)
• Embedded – C, C++
• Database – PostgreSQL, SQL Server, MySQL

Yes, we do.

• Ecommerce
• Retail Stores
• Healthcare
• Finance
• Energy Services
• Restaurant & QSR
• Media & Gaming
• Energy Management
• Many more…

There’s a list of a few recent clients on our company's website. Unfortunately, due to confidentiality limitations, we can’t share project information till we realize there’s a good fit and we get a mutual NDA in place. At that time, we will send over portfolio work and a full list of references.

Yes, every one of our projects is architected with an API layer.

Yes, we’ve dealt with HIPAA compliance on some large-scale, multi-year projects in the healthcare space and PCI compliance is a thing we manage on a regular basis since 80% of our Projects require the processing, transmission or storage of credit card data. IWebSquare is also a certified Authorize.net development partner.

On request, we can offer our entire security and compliance package which highlights our policies and practices regarding data handling, Security, and all other safeguards. This approach also incorporates all Policies linked to our hosting packages.

Yes. We've got a private cloud on both Rackspace and Azure which we host and control our clients’ applications. We Host as well as manage products that thousands of users depend on each day. Uptime in our production environments hasn't ever been a concern.

• Container for services including transactional email, notification, batch reporting, and so on.
• Sandbox environments for development, testing, and staging
• Regular OS updates
• Nightly web server and database backups
• Ongoing bot and attack monitoring
• Performance monitoring and event logging
• Standardized recovery mechanisms

Yes. On request, we can offer our entire security as well as compliance package which features our policies as well as practices when it comes to data management, security, and all other safeguards. This approach consists of all Policies associated with our hosting packages.

While nobody is ever totally secure, we are proud of the fact that none of our clientele has ever been brought down by an attack and that our network hasn't ever faced a breach.

We have in no way had to face an emergency recovery scenario, but we inevitably carry out nightly backups to help in fast recoveries. In some instances, we backup data every couple of hours. Our recovery response time is lower than 24 hours.