The right partner saves months. Ask these questions before signing.
- Can I open stores you have built?
- What exactly is in the quote, and what is extra?
- Who owns the code, design and data?
- How is support handled after launch, and how fast?
- How will we communicate during the project?
- What happens if I want to move to another vendor later?
A good company answers plainly, in writing, and is happy to be compared.
Why the choice matters so much
An online store is not a one-off purchase like a laptop. It becomes the main way customers find, trust and pay you, and it must keep working, stay secure and grow with the business. The company that builds it will shape your costs and options for years. A good partner saves months and money. A poor one leaves you with a slow store, hidden costs and code you cannot move. This guide gives you a process to choose well, with questions, red flags and a way to compare quotes fairly.
Step 1: Know what you are buying
Before you contact anyone, write a short brief. It does not need to be technical. Cover who your customers are, what you sell, how many products you have, how orders are taken and delivered today, which payment methods you want, which systems must connect (accounting, ERP, courier, WhatsApp), whether you need an Android and iOS app, which countries you will sell in and what your realistic budget and timeline are. A clear brief produces comparable quotes and shows which companies listen.
Step 2: Understand the types of providers
- Freelancers. Often the cheapest and most flexible, but a single person can become a risk if they are unavailable. Ask who covers when they are away.
- Small agencies. Usually offer design, development and support under one roof with more resilience than a freelancer.
- Large agencies. Strong process and capacity, but higher cost and sometimes less attention for small projects.
- Platform companies and product vendors. Fast to start on their own system, but check how much you can customise and whether you can leave with your data.
- Specialist e-commerce developers. Focus on stores and apps, understand payments, stock and logistics and usually integrate well with local services.
None is automatically best. Match the provider to the size and complexity of your project.
Step 3: Check proof of work
Ask for live examples you can open on your own phone. Test the speed, try the checkout, search for products and look for errors. Ask what part of each project the company built, because agencies sometimes show work done by partners. Read independent reviews and, for larger projects, ask to speak with a past client. Pay attention to how long the stores have been live and whether they are still updated, since a store that looks good at launch but is abandoned a year later tells you about support quality.
Step 4: Ask about process and communication
A reliable company can explain how it works in plain language: discovery, design approvals, development stages, testing, launch and support. Ask who will be your point of contact, how often you will receive progress updates, which tools are used for tracking tasks and how change requests are handled. Check response times during your trial conversation. If they are slow while selling, they will be slower after payment.
Step 5: Compare quotes properly
Two quotes for “an online store” can differ by multiples because they cover different things. Build a comparison table with these rows and ask each company to fill it in:
- Number and type of pages and templates
- Catalogue size and import support
- Payment gateways and methods included
- Shipping and courier integrations
- Tax and invoice setup
- Accounting or ERP integration
- Mobile app, if needed, and platforms covered
- Admin features and user roles
- Speed, search and security setup
- Content migration
- Training and documentation
- Testing and launch support
- Hosting, backups and monitoring
- Post-launch support period and what it covers
- Payment schedule and what happens if scope changes
Our cost guide explains how scope drives price. A cheap quote that leaves out half of this list is not cheap.
Step 6: Ownership and exit
Insist on clarity about ownership before you sign. You should own your domain, hosting account, source code, design files, customer data and content, or at least have the right to receive them in a usable form. Ask what happens if you want to change provider: how long handover takes, whether there are fees and whether the code is documented. Beware of proprietary systems that lock you in without a way to export your products and customers.
Step 7: Security and maintenance
The October 2026 PHP alert showed how quickly an unpatched server becomes an emergency. Ask who will patch the server and platform, how often backups run and where they are stored, how quickly the company responds to security issues, what monitoring is included and what the written response time is. Ask how admin accounts are protected and whether you get separate logins and two-step verification. For apps, ask where the back end runs and who keeps it updated.
Step 8: Contract and payments
A fair contract states the scope, deliverables, timeline, payment milestones, acceptance criteria, support terms, ownership and confidentiality. Prefer payments tied to delivered milestones rather than most of the money up front. Keep a reserve until the store is live and tested. Make sure change requests are priced and approved in writing.
Red flags
- A price far below every other quote with no explanation
- No live examples or examples they cannot explain
- Pressure to pay quickly or decide today
- Vague scope, “unlimited” promises or refusal to put things in writing
- Unwillingness to share ownership of code and data
- Poor communication before the contract
- No plan for support, security or backups after launch
- Reviews that look copied or cannot be verified
Green flags
- Clear questions about your business before they quote
- Honest advice, including telling you what you do not need yet
- Written scope with milestones and acceptance tests
- Visible stores built by the team, with working checkout and good mobile speed
- Plain-language explanations and quick, consistent replies
- Handover of code and accounts in your name
- A written support plan with response times
Run a small paid trial
If the project is large, start with a small paid piece such as a design sprint, a technical audit or a single module. It lets you test communication, quality and delivery speed before committing the full budget.
Questions to ask in the final meeting
- Who exactly will work on my project, and what is their experience?
- What are the three biggest risks you see and how will you handle them?
- What will I need to provide, and by when?
- How do you test before launch?
- What happens in the first month after launch?
- What does it cost to keep the store running each month?
- How would we handle a security incident?
Why businesses choose NNT Mart
NNT Mart builds online stores, B2B portals, marketplaces and Android and iOS apps, quotes scope and support separately, hands over code and accounts in your name and agrees patching, backups and monitoring in writing. Share your brief through the contact form or WhatsApp and we reply within minutes with questions, a plan and a clear quote.
How NNT Software can help
NNT Software is happy to be compared. We quote scope and support separately, tell you which technology we would use and why (API-first back end, Flutter apps, cloud deployment), hand over code and accounts in your name and agree patching, backups and monitoring in writing. Send your brief with the comparison table above and we will fill in every row.