MIXEDIT consulting in Naples: how to choose a technology partner
Choosing who supports you on software, data and automation is a decision that weighs for years: a good partner saves time and money, the wrong one leaves you with a half-finished system and a quote to redo. We're an IT consulting firm based in Naples, so we're an interested party — which is why we'd rather give you the questions than the answers. The advice applies anywhere, whether you're a local SME or a company looking for a partner in southern Italy.
The 8 questions to ask before signing
- "Have you done a project similar to ours?" Not "do you have experience" — ask for a concrete case, with what went well and what went badly. Anyone who's never had problems has never done projects.
- "What do you need from us?" A serious partner will ask for your people's time, access to data, quick decisions. Anyone who says "we'll take care of everything" doesn't know projects.
- "What happens after go-live?" Who provides support, how quickly they respond, what it costs, how changes are handled. This is where most disagreements start.
- "Who owns the code and the data?" You must be able to change supplier without losing anything. If the answer is vague, get it in writing.
- "How will we measure whether it worked?" Hours saved, fewer errors, response times: if the supplier doesn't propose indicators, propose them yourself.
- "Which technologies and why?" You don't need to understand the technical answer; you need to see whether they can explain it and whether they lock you into something with no exit.
- "Who will actually work on the project?" The person you talk to during sales isn't always the one who develops. Ask to meet the technical lead.
- "What is NOT included?" The most useful question of all. An honest supplier has a list ready.
Warning signs
- Promises everything without asking questions. A quote that arrives after a ten-minute phone call can't be serious.
- A price much lower than the others with no clear explanation of what's been left out.
- Lock-in: proprietary platforms you can't export data from, fees that double on renewal.
- No adoption plan: the software works, but nobody in the company uses it because nobody guided them.
- "AI will solve everything." AI solves specific processes. Anyone who pitches it as a universal answer doesn't know it well (see 7 concrete uses of AI for SMEs).
What a serious quote should include
| Section | What to look for |
|---|---|
| Goal and scope | Written in plain language: what the system will do and for whom |
| Included / excluded | An explicit list, including integrations and data migration |
| Phases and deliverables | Verifiable milestones, not a "final delivery" in six months |
| Roles | Who does what, including on your side |
| Recurring costs | Licences, hosting, support, AI model usage |
| Ownership and exit | Code, data, exportability, what happens if you part ways |
| Support | Channels, response times, cost of changes |
Does proximity still matter?
For pure development, less than it used to: remote work works well. For projects that affect processes — management systems, automation, data — yes: understanding how a company really works means seeing it, and people's adoption needs close support in the first weeks. A partner in Naples or Campania can be at your premises within an hour and understands the context you work in: the kind of customers, suppliers and timelines.
Why proximity made the difference. In the construction companies that replaced Excel sheets with V-Site, the most delicate part wasn't technical: it was getting workers to clock in with the QR code and convincing site managers to give up their spreadsheets. We did it by going on site, not by sending a manual. The hours recovered every week by the office, site managers and workers came only once the system had become "the normal way of working" — and that's built in person.
How we work (transparently)
We start with a free 30-minute consultation where we ask questions rather than give presentations. If there's a sensible project, we propose a small, measurable pilot before any big commitment. The code and data are yours. And if the problem can be solved with an existing system or a configuration change, we tell you — even if it's not something we sell.
Frequently asked questions
Is a local or a remote software house better?
For process projects proximity matters; for well-specified development less so. Ideal: close by, but able to work remotely too.
What should a serious quote include?
Scope, included/excluded, phases, roles, recurring costs, ownership of code and data, support.
What are the warning signs?
Promises without questions, anomalous price, lock-in, no adoption plan, "AI solves everything".
Ask us the 8 questions
Free 30-minute consultation, in Naples or remotely: tell us the problem and we'll tell you what makes sense.