Author: Sanjan Sharma

Choosing a shopify development partner is mostly a question about restraint. The platform does a great deal out of the box, and the agencies that produce the best results are usually the ones arguing for less custom work rather than more.

Here are eight questions that surface how a shopify development partner actually thinks.

1. What would the shopify development partner refuse to build?

A good shopify development partner answer is specific and slightly deflating: a custom checkout you do not need, a bespoke feature an existing app covers, a redesign when the problem is page speed. An agency that agrees to everything is quoting rather than advising.

2. Theme customisation or a custom build, and why?

Most stores are well served by a solid theme carefully customised, since it keeps you compatible with updates and with the wider app ecosystem. A fully custom front end makes sense at real scale or where the shopping experience is genuinely unusual. Ask which they are proposing and what it costs you in flexibility later.

3. How many apps will I end up with?

Apps are the quickest route to a feature and the most common cause of a slow, fragile store. Each one adds scripts, a monthly fee and another thing that can break during a platform update. Ask how they decide between an app and building something small, and ask who audits the list annually.

4. What is the shopify development partner’s approach to speed?

Ask for a live store they built and check it yourself on a phone, on mobile data. Google’s page experience documentation explains what is being measured, though you will notice a slow store without any of it. Conversion and speed move together more reliably than almost anything else on a store.

5. Who owns the store when we part ways?

You should own the Shopify account, the theme code, the domain and any custom app. Ask for that in writing. Ask too whether the theme lives in a repository you can access, because a theme edited only in the admin has no history and no way back from a bad change.

6. How do you handle data and checkout changes?

Customer data, abandoned cart flows and anything touching checkout carry obligations and platform restrictions. A partner who has worked at any scale will raise this unprompted, including what is and is not permitted outside the enterprise plan.

7. What does shopify development partner support look like after launch?

Stores break on Black Friday, not on a quiet Tuesday. Ask about response times, who is on call, and what counts as included versus billable. Then ask what they charge for an urgent fix outside hours, because the answer tells you how they think about the relationship.

8. A shopify development partner should show you a store that struggled

Every shopify development partner has one that underperformed. What you are testing is whether they can say what went wrong and what they changed. An agency with only successes is either very new or not going to be straight with you when it is your turn.

Shopify development partner questions we are asked

Does a shopify development partner need to be a Shopify Plus partner?

Only if you are on Plus or heading there. The badge indicates volume of work on the platform rather than quality of judgement, so use it as a filter and not as the decision.

What should a shopify development partner charge?

Theme customisation is a project of weeks; a custom front end is months and a different order of cost. Ask which is being proposed before comparing two numbers, because they are not the same purchase.

Can we change shopify development partner mid-build?

Yes, and it is far less painful where the theme lives in a repository you own and the store is in your own Shopify account. That is the real reason to insist on both at the start.

What usually matters more than the build

Pick your shopify development partner on judgement rather than on a feature list. Product photography, how clearly the pages answer buying questions, and how quickly the site loads on a phone. Those three move revenue more reliably than most custom development, and all three are cheaper than a rebuild. A partner who leads with them is telling you something useful about where they think the value is.

Our ecommerce development page sets out how we build and maintain stores, and the ecommerce growth page covers what we do once one is live.

The cost of online reputation management is quoted in a wide range for the same reason legal fees are: the work is partly predictable and partly dependent on how bad the situation is. A monitoring retainer and a live crisis are different products sold under the same name, and most confusion about pricing comes from that.

Here is what actually drives the cost of online reputation management.

1. What is on page one sets the cost of online reputation management

Displacing a weak result from a low-authority site is ordinary work. Displacing a national news article is a long campaign, and sometimes it is not achievable at all. Any quote given before someone has looked at your actual results is a template.

2. How many names you protect multiplies the cost of online reputation management

A company name alone is one problem. A company plus three executives plus a product plus the variations with “reviews” and “complaints” attached is five or six problems, each needing its own pages. This is usually the single largest multiplier.

3. Whether you can publish

The cheapest version of this work uses assets you control: your site, your profiles, your listings, your team’s professional pages. If you have those and can publish to them quickly, a great deal of progress costs only coordination. If every page needs legal approval and a three-week cycle, the same work takes months and is priced accordingly.

4. Monitoring and intervention are priced differently

Monitoring is a modest ongoing fee for alerts and a monthly review. Intervention is project work. Confusing the two is how businesses end up paying a retainer for years and feeling they received nothing, since nothing happening is exactly what the retainer buys.

5. Review generation is often the cheapest fix

Where the problem is a thin review profile rather than a search result, the answer is usually a process for asking satisfied customers at the right moment. That is a small piece of work. Never incentivise ratings, though, because platforms detect it and the penalty is worse than the original problem.

6. Legal work is separate and it is not cheap

Defamation, impersonation and genuine privacy breaches need a lawyer, not a marketing agency. Agencies that offer takedowns as a bundled service are usually describing platform reporting forms, which you can submit yourself for nothing.

7. The real cost of online reputation management is time

Search results move over months. A six-month engagement that is reviewed honestly at month three is a sensible structure; a twelve-month contract with no break clause is a sales structure. Agree what progress looks like at the halfway point and what happens if it has not appeared.

Before any of this, the United States Federal Trade Commission’s guidance on removing personal information online covers the free routes that exist, and it is worth exhausting those first.

What you can reasonably do yourself

Much of the cost of online reputation management is avoidable. Claim every profile carrying your name, fill in the listings properly, publish two or three useful pages on your own site, and set up a free alert on your brand terms. That is a weekend of work and it resolves a surprising share of mild cases, which also makes any quote you then request smaller and more specific.

Common questions about the cost of online reputation management

Is the cost of online reputation management ever a one-off?

For a thin review profile or a weak result on a small site, yes, and that is the cheap end of the range. Anything involving an established result on a strong domain is a programme, because displacing it depends on publishing over months.

Why do quotes for online reputation management vary so much?

Because the name covers monitoring, publishing, review generation and crisis handling. Ask which of the four a quote includes and most of the variation turns out to be scope rather than rate.

Can the cost of online reputation management be fixed in advance?

Partly. The publishing and monitoring elements price cleanly. What cannot be fixed is a new negative result appearing mid-engagement, so settle in the contract how that is handled before it happens.

Questions that stop a quote drifting

Ask what is included when a new negative result appears mid-engagement, whether content production is in scope or billed separately, how many names the fee covers, and what the exit looks like. Get those four in writing and the number you were quoted tends to be the number you pay.

Our digital PR page covers the publishing side that does most of the work here, and the public relations page covers handling a story while it is still live.

Custom mobile software development is priced as a build and lived with as a commitment. The quote covers writing the thing; the cost covers keeping it alive on two platforms that change every year, which is the part that surprises people in month fourteen rather than month two.

Here are seven custom mobile software development lessons, in the order they usually arrive.

1. Three decisions set most of the custom mobile software development budget

Whether it works offline, whether it needs real-time updates, and whether it must behave identically on both platforms. Each one roughly doubles the engineering in its area, and all three are decided in conversation rather than in code. Settle them before the estimate, since an estimate against an unsettled brief is a guess wearing a number.

2. Offline is a different product

“It should work on the train” sounds like a feature and is an architecture. Data has to be stored locally, changes have to be queued, and two people editing the same record offline have to be reconciled when they reconnect. If your users are genuinely offline sometimes, build for it from day one. If they are not, say so out loud and save the money.

3. In custom mobile software development the backend is the larger half

People picture screens, and the screens are the visible part. Authentication, permissions, notifications, syncing, an admin interface and the reporting someone will ask for in month three all live behind them. When a quote looks low, this is normally what is missing.

4. Custom mobile software development needs a release rhythm

App store review adds days, users update on their own schedule, and you will be supporting two or three versions at once for a while. So plan releases as a rhythm rather than as events, and make sure the app can tell a user, politely, that their version is too old.

5. Device testing finds what simulators do not

Older phones, small screens, poor connections, low battery modes and the accessibility settings people actually use. Keep a small shelf of real devices, including one that is four years old, because that is what a meaningful share of your users carry.

6. Permissions are a design problem

Location, camera, notifications and contacts each need a reason the user understands at the moment you ask. Ask badly and they decline permanently, which quietly breaks the feature for that user forever. Apple’s privacy guidance in the Human Interface Guidelines is short and worth reading before the screens are drawn.

7. Decide who owns it in year two

Platform updates, library deprecations, certificate renewals and store policy changes arrive whether or not you have a team. An app left alone for eighteen months often will not build, let alone run. Budget maintenance as a line item from the start, and name the person or the agreement that covers it.

Custom mobile software development questions we are asked

What does custom mobile software development cost?

The three decisions in lesson one move the figure more than the screen count does, which is why quotes given against a feature list alone vary so widely. Settle offline, real-time and platform parity, and the range narrows sharply.

Is custom mobile software development worth it over an off-the-shelf app?

Only where the workflow is genuinely yours. If a packaged product covers it with awkward edges, the awkward edges are usually cheaper than a build plus a decade of maintenance.

Who maintains custom mobile software development after launch?

Decide before you sign: your team, the original builder under an agreement with a named response time, or a third party with a documented handover. Certificates and platform updates do not wait for the question to be settled.

Where projects go over, in our experience

Custom mobile software development rarely goes over on the screens, which are estimated carefully because everyone can picture them. It goes over in the admin interface nobody specified, the reporting requested in month three, and the week lost to a store rejection that a half-hour of reading would have avoided. None of those are surprises in general, only in particular.

What a sound estimate contains

A sound custom mobile software development estimate contains a short discovery phase with its own price, those three decisions written down as answered, the backend scoped separately from the screens, a named list of devices to be tested, and a maintenance figure for year two. An estimate missing any of them is not wrong so much as incomplete, and the gap will be filled later at a worse moment.

Our custom software development page sets out how we phase this, and the mobile app development page covers the store and release side in more detail.

Every marketing automation platform demos well, because demos run on clean data, a simple funnel and a presenter who knows exactly where to click. Your situation has none of those, so the useful evaluation is one that deliberately breaks the demo conditions.

Here are eight marketing automation platform tests, in the order we would run them.

1. Import your own messy data into the marketing automation platform

Not the sample file. Ask for a trial and load two thousand of your real contacts, including the duplicates, the missing fields and the three spellings of the same company. How the system handles that is how it will handle your Tuesdays.

2. Build your actual worst workflow

Pick the most awkward sequence you run today, the one with exceptions and a manual step. Build it in the trial. If it takes a consultant, you have learned the real cost of ownership before paying it.

3. Count the seats you actually need

Pricing pages quote a tier, and then sales operations, a designer and an agency all need access. Ask what an extra user costs, what a read-only user costs, and whether a contractor can be added for a month.

4. Ask how contacts are counted

This is where the bill grows. Does an unsubscribed contact still count? A bounced one? A record created by a form test? Get the counting rule in writing, then estimate your number in two years rather than today.

5. Try to leave the marketing automation platform

During the trial, export everything: contacts, activity history, email templates, workflow definitions. Some of it will not come out cleanly, and knowing which part is captive is worth a great deal at renewal time.

6. Check the consent and privacy handling

How consent is recorded, how a deletion request is honoured across activity history, and where data is stored. If you reach European or Canadian contacts the requirements are specific; the Office of the Privacy Commissioner of Canada’s guidance on online tracking is a readable starting point.

7. Find out what marketing automation platform support means at your tier

A named contact, a chat window or a knowledge base. Ask for the response time at the tier you would actually buy, not the one in the demo, and ask what happens at five in the afternoon on a Friday.

8. A marketing automation platform is only as good as the data going in

The honest test is whether your CRM is currently trustworthy. If leads are entered inconsistently and nobody updates stages, automation will make that mess faster rather than better. Fixing the inputs first is unglamorous and it is the difference between a platform that pays for itself and one that becomes a monthly complaint.

Who runs it after the first month

A marketing automation platform needs an owner. Someone has to own the workflows, retire the ones that stopped making sense, and keep the field names consistent. Without that, a platform degrades quietly: half the automations still fire, nobody is sure which, and the reporting slowly stops being believed. Name the owner during the evaluation, not after.

Marketing automation platform questions we are asked

Do we need a marketing automation platform at all?

Not if nobody owns the CRM. A marketing automation platform multiplies whatever discipline already exists, so where lead stages are not maintained the honest first purchase is the process, not the software.

Can one marketing automation platform replace the CRM?

Some claim to and it works at small scale. Once sales has its own pipeline discipline, keeping the two separate and integrated usually ages better than one tool doing both adequately.

What does a marketing automation platform really cost?

Estimate the licence at twice your current contact count, then add implementation and the seats nobody counted. That total, not the tier price, is the comparison.

What usually decides it

Run the eight tests and the marketing automation platform shortlist usually collapses to one. In practice the choice comes down to three things: whether it connects to the systems you already run, whether your team can build a workflow without help, and what it costs at twice your current contact count. Feature comparisons rarely change the answer, although they absorb most of the evaluation time. Buy the one your team can operate without a consultant on retainer, and accept that it will be missing a feature you thought you needed.

Our CRM and marketing automation page covers how we implement these, and the B2B lead generation page explains what we put through them.

Custom erp software development is one of the few remaining projects where a business can spend a year’s budget and end up worse off than when it started. It is also, occasionally, exactly the right decision. The difference is almost always visible at the start, and almost always ignored.

Here are the custom erp software development traps, and the test we apply before agreeing to build anything.

1. Custom erp software development that rebuilds the broken parts

The fastest way to a disappointing system is to document the current process and recreate it. Existing processes contain workarounds for problems that no longer exist, steps that exist because one person preferred them, and duplicate entry nobody questioned. Build those in and you have paid to make them permanent.

So map the process, then ask of each step why it exists. Expect a quarter of them to have no answer.

2. Underestimating the data custom erp software development has to carry

Your stock codes, customer records and historic transactions are the real project. They live in several systems, they disagree, and reconciling them is slow work that nobody finds interesting. Give it its own phase and its own owner, because when it is treated as a final step it becomes the reason you go live late.

3. Choosing custom erp software development before testing configuration

Established packages cover more than they did five years ago. The honest test is whether your genuinely unusual requirements are the ones that make you money. If the unusual parts are pricing rules or a production process that is your competitive advantage, building is defensible. If they are invoice layouts and approval chains, you are paying to avoid changing habits.

4. No single decision maker

Custom erp software development touches every department, and every department has a view. Without one person empowered to settle disputes quickly, the specification grows to satisfy everyone and the project slows under its own weight. Name that person before the first workshop.

5. Training treated as the last line of the plan

The system will be used by people who did not attend the workshops and did not want a new system. Budget for training that happens twice, once before go-live and once a month after, when staff have real questions rather than hypothetical ones.

6. No answer for who maintains it in year three

Custom erp software development is a commitment, not a purchase. Someone has to apply updates, fix what breaks and make changes as the business changes. Decide now whether that is your team, the original builder, or a maintenance agreement with a named response time, and get it in writing while you still have leverage.

On the security side, the United States Cybersecurity and Infrastructure Security Agency’s secure by design guidance is a reasonable checklist to hand your supplier before the architecture is fixed.

When custom erp software development is the right call

Three conditions together, in our experience. The process that makes you money is genuinely unusual, no package handles it without being bent out of shape, and you have someone internal who will own the system for years rather than months. Two out of three is a configuration project with extra steps.

Custom erp software development questions we are asked

How long does custom erp software development take?

Phased properly, the first department is a matter of months and the whole business is a matter of years. Projects quoted as a single twelve-month delivery across every department are the ones that get abandoned at month nine.

Is custom erp software development cheaper than a licence?

Almost never over five years once maintenance is counted. It is justified by fit rather than by price, so if the argument being made to you is cost, ask to see the five-year comparison.

Can custom erp software development be done in stages?

Yes, and it should be. Build the one process that is genuinely yours, integrate standard packages around it, and leave the rest alone.

The test worth applying first

Write down the three things your business does differently from competitors. If an off-the-shelf package can handle those three, configure it and spend the saved budget elsewhere. If it genuinely cannot, build only those three and integrate the rest, since a small custom core around standard components is usually the cheapest version of this decision.

Our CRM and ERP development page sets out how we scope these, and the API integration page covers connecting a custom core to the packages you keep.

Choosing a lead generation company is difficult because the thing being sold is a promise about the future, and everyone’s deck promises the same future. The useful signals are not in the pitch; they are in what the company is willing to show you and what it declines to.

Here are nine we would want checked on us, or on any lead generation company you are considering.

1. They ask who your best customer is, early

Good work by a lead generation company starts with a narrow target, so the first conversation should include questions about which deals closed fastest and which went nowhere. A company that takes a brief and starts immediately is optimising for its own start date.

2. The lead generation company will show a dashboard

Not a case study, which is a story the company wrote about itself, but the actual tool with the actual numbers. We publish walkthroughs of our own four accounts for this reason: 5,076 LinkedIn invitations produced 1,086 replies and 370 booked sales calls, and anyone can watch where each figure comes from.

The ratio matters more than the totals. Replies are plentiful and booked calls are not, so a proposal implying otherwise deserves a question.

3. The definition of a lead is in writing

A form fill is not a lead. A booked call with someone who can sign is a lead. Agree it before the contract, and agree what happens to a no-show, because that is where optimistic reporting lives.

4. They tell you what they need from you

Product answers, a calendar that is actually open, someone to take the calls, and a decision when a message needs approving. A lead generation company that claims to need nothing from you is describing a campaign that will run on generic copy.

5. Compliance comes up without you raising it

Email and calling are regulated, and the rules differ by market. The United States Federal Trade Commission’s CAN-SPAM compliance guide is the baseline for email, and a company working across borders should be able to say how it handles the equivalents elsewhere.

6. A good lead generation company names what it will not do

Expertise shows up as exclusion. A company that offers every channel at once has either a very large team or a very flexible definition of the word offer.

7. The lead generation company reporting shows the bad weeks

Ask to see a report from a month that went badly. Every real account has one. What you are testing is whether the reporting was built to inform you or to reassure you, and you can only tell by looking at a bad month.

8. There is a stop condition

A cost per booked call above which this does not make sense for your business, agreed in advance and written down. A company that cannot imagine recommending less spend is paid in a way that conflicts with your result.

9. You can speak to a client who left

Uncomfortable and informative. References who stayed tell you what works, while a client who left tells you how the lead generation company behaves when things go wrong, which is the part you need.

Lead generation company questions we are asked

What does a lead generation company cost?

Either a monthly retainer or a price per booked meeting, and the second looks cleaner than it is, because the definition of a meeting then decides your invoice. Whichever model you pick, settle the definition first.

Should a lead generation company use our domain or their own?

Their own sending infrastructure for cold volume, with your brand in the message. Burning your primary domain’s reputation is a cost nobody prices in the proposal.

How soon should a lead generation company produce meetings?

First meetings inside a month, a fair verdict at sixty days. Earlier than that you are judging setup rather than performance.

What none of these tell you

Whether the market wants what you sell. If the offer is unproven, outbound will produce conversations that go quiet, and the cause will look like the agency. So before you buy volume, be able to name three customers who bought recently and say why, because that is the brief a lead generation company actually needs.

Our B2B lead generation page sets out the sequence we run, and the four-account case study has the recordings behind every number above.

Every business eventually gets the email: you have been shortlisted, the ceremony is in March, tables are available. Business rate awards occupy an odd space between genuine recognition and a paid marketing product, and the difference is not always visible from the invitation.

Here is how to tell them apart, and when entering is worth the effort.

1. Work out who pays for the business rate awards programme

Some awards are funded by entry fees, some by ticket sales, some by sponsors, and some by the winners buying logo licences afterwards. None of those is disqualifying on its own. However, if the revenue comes mostly from winners, expect a lot of winners.

A quick check: count last year’s categories. Forty categories with three winners each is a marketing product, whatever the branding says.

2. Read the business rate awards judging criteria before the entry form

Real business rate awards publish who judges, what they score, and how. Vague criteria usually mean the decision is editorial, which is fine if the publication matters to your buyers and worthless if it does not.

3. The business rate awards entry is the value, even if you lose

This is the part people miss. Writing a good entry forces you to state what you did, for whom, and what changed, with evidence. That document then feeds your website, your proposals and your case studies. Several of our strongest client write-ups started as award entries that did not win.

4. Evidence beats adjectives, every time

Judges read dozens of entries that all describe themselves as innovative and customer-focused. The ones that stand out contain specifics: what the situation was, what you changed, what the number did, and what you would do differently. Dashboard screenshots and client quotes do more than another paragraph of description.

5. Check what you may actually claim afterwards

Most programmes restrict how you use the logo, for how long, and whether finalists may call themselves anything. Beyond the programme’s own rules, how you describe an award in advertising is regulated, and the United States Federal Trade Commission’s advertising guide for small business is a clear summary of the line between confident and misleading.

6. Local business rate awards usually beat national ones

A regional or trade award your buyers recognise is worth more than a national badge nobody in your market has heard of. The reach is smaller and the credibility is specific, and specific credibility is what actually helps in a sales conversation.

7. Decide the budget as marketing, not as recognition

Business rate awards cost more than the entry fee: the time to write, the tickets, the travel and the logo licence add up quickly. Judge the whole figure against what else that money could do, because emotionally this is about recognition and financially it is a campaign.

When business rate awards are genuinely worth entering

Three conditions, roughly. Your buyers already know the name, the categories are few enough that winning means something, and you have a piece of work from the last year with evidence attached. Meet all three and the entry is a good use of a week. Meet one and it is a logo.

Business rate awards questions we get asked

Do business rate awards actually win work?

Indirectly. They rarely create an enquiry on their own, and they do shorten the trust conversation when a buyer already recognises the name. Treated as proof rather than promotion, business rate awards earn their place.

Is it worth paying to enter business rate awards?

Only where the name means something to your buyers and the categories are few. A fee for a programme with forty categories is advertising, which can still be a reasonable purchase as long as you budget it as one.

Who should write the business rate awards entry?

Whoever did the work, with an editor. Entries written entirely by marketing read as adjectives, and judges are reading for evidence.

A quick way to triage an invitation

Four questions. Who judges it, how many categories are there, what does winning cost in total, and would one of your buyers recognise the name unprompted? If the answers are unclear, unclear, large and no, then it is advertising, and you can judge it as such without feeling churlish.

If you want help writing the entries, our awards and recognition page covers how we approach them, and the digital PR page explains how a win becomes coverage rather than a logo in a footer.

Teams plan the build and then discover that system development integration is the project. The features were understood, the joins between systems were not, and the schedule was written as though connecting two things is a task rather than a phase.

Here are six system development integration rules we hold to, each one learned the expensive way.

1. Start system development integration earliest, not last

The instinct is to build each piece properly and connect them at the end. However, that saves nothing, because every assumption you made about the other system stays unchallenged until the worst possible moment. Make a thin end-to-end path work in week one, even if it carries one field and does nothing useful.

After that, every later change is tested against something real rather than against a document.

2. The other system’s documentation is a hypothesis

It will be out of date somewhere, and the gap is rarely flagged. So call the real endpoint early, record what comes back, and keep those recordings as fixtures. When the behaviour changes six months later, you will have evidence of what it used to do.

3. Decide what system development integration does when the other side is down

Not if. Every integration has an outage, a timeout and a slow day. Decide per call whether the right behaviour is to queue, to retry, to fail visibly or to carry on without it, and write that decision next to the code.

Retries need care too, since a retried payment or a retried email is worse than a failure. Make the operation safe to repeat, or make it impossible to repeat.

4. Agree who owns the truth for each field

When two systems both hold a customer’s address, one of them is right and the other is a copy. If nobody has decided which, you will get a loop where each system updates the other and support cannot explain why the address keeps changing. Write the ownership down per field, not per system.

5. Log the conversation, not just the result

When something goes wrong between two systems, the question is always what was actually sent and what actually came back. Store both, with a correlation identifier that appears in every log line, and redact what should not be kept. This costs very little and saves days.

6. System development integration needs a named owner on both sides

The hardest system development integration problems are organisational. A question about a third-party system takes a day to answer if you know who to ask and a fortnight if you do not. Get a name and a channel before the work starts, and escalate early when answers stop arriving, because waiting politely is the most common cause of a slipped date.

For the architectural side, Martin Fowler’s article on microservices remains a clear explanation of the trade-offs you are accepting when you split systems up in the first place.

System development integration questions we get asked

How much of a project is system development integration?

More than the plan says, routinely a third to a half once you count the failure handling, the field ownership arguments and waiting on answers from other teams. Scheduling it as a phase rather than a task is most of the fix.

Who should own system development integration?

One named engineer on your side and one named contact on each external system. Shared ownership here reliably produces the slowest version of every answer.

Does system development integration need its own test environment?

Yes, and the recorded-response fixtures described above matter more. A sandbox tells you what the other system claims to do; recordings tell you what it actually did.

What good looks like six months in

System development integration stops being the risk. Nobody is surprised by an outage, because the behaviour was decided in advance and is visible in the logs. A new field takes an hour rather than a meeting, since ownership is already written down. And when the third party changes something, you find out from a failing fixture rather than from a customer.

What to put in the plan

A system development integration plan needs four things: a thin end-to-end path in the first week, a named contact for every external system, a written decision on failure behaviour per call, and field-level ownership. Those four take an afternoon to agree and they remove most of the surprises.

Our API integration page sets out how we run this, and the custom software development page covers how it fits into a wider build.

Almost every business we talk to is being sold ai automation, and almost none of them have been told where it reliably works. The honest answer is that it pays off in narrow, unglamorous places and disappoints in exactly the places the demos focus on.

Here is the split, based on what we have shipped and what we have had to unpick.

Where ai automation actually pays

1. Ai automation for documents that arrive as a mess

Invoices, purchase orders, delivery notes and forms in twelve different layouts. This used to be a project; now it is a short piece of work with a review step, and the saving is immediate because the task was pure transcription.

2. Routing and triage

Sorting inbound email or tickets into the right queue with the right priority. The model does not need to be right every time, since the fallback is the queue the item would have sat in anyway.

3. Ai automation that drafts the first version

Replies, summaries, job descriptions, product copy. A human still edits, so the gain is in the blank page rather than the final text, and that is still a real gain.

4. Structuring free text

Turning call notes, survey answers or reviews into fields you can filter. This is dull and it is where a lot of quiet value sits, because the data existed and was simply unusable.

5. Ai automation for internal search that answers

Pointing a model at your own documents so staff get an answer with a citation rather than a list of files. Insist on the citation, otherwise you cannot tell a good answer from a confident one.

6. Checks that nobody enjoys

Comparing a contract against a checklist, or flagging anomalies in a report before a human reviews it. Framed as a second pair of eyes rather than a decision maker, this works well.

7. Handover notes and logging

Summarising what happened on an account or a shift, so the next person starts informed. Small, and it compounds.

8. Connecting the systems you already pay for

Much of what gets sold as ai automation is ordinary integration work with a model doing one step in the middle. That is not a criticism, because the integration is usually where the value was.

Four ai automation myths that waste budget

1. It removes headcount in the first year

Ai automation removes tasks. Those tasks are spread across people, so the effect shows up as capacity rather than as a smaller payroll, and anyone promising otherwise is selling.

2. Accuracy is a solved problem

It is not, so design ai automation for being wrong. Every workflow needs a review step, a confidence threshold or a reversible action. The United States National Institute of Standards and Technology’s AI Risk Management Framework is a practical starting point for deciding how much review a given task needs.

3. You need your own model

Almost nobody does. The ai automation work that matters is in the data you feed it, the prompt, and the handling of failures, none of which requires training anything.

4. Start with the most visible process

Tempting and usually wrong. Start with something low risk, high volume and easy to check, because the first project teaches you how to run the second one, and you want that lesson to be cheap.

Ai automation questions we get asked most

Where should a first ai automation project start?

With a task that is high volume, low risk and easy to check, because the point of the first project is to learn how your organisation reviews and corrects machine output. Companies that begin with something customer-facing learn the same lesson at a much higher price.

Does ai automation need clean data?

Less than it used to, which is most of what changed. Handling inconsistent documents is now one of the things it does well. What it still needs is a clear definition of a correct result.

How is ai automation different from the automation we already have?

Rules-based automation does exactly what you specified. Ai automation handles the steps where the rule could not be written down, and in exchange it is occasionally wrong, so it belongs behind a review step.

How to pick the first one

Good ai automation starts small. Find a task done more than fifty times a week, where a wrong answer is visible and cheap to fix, and where someone can tell you today what “correct” looks like. If no task meets all three, the right first step is measurement rather than automation.

Our AI and automation page sets out how we scope these, and the API integration page covers the plumbing that most of this work turns out to be.

Buying school management software is unusual as purchases go, because the people who choose it are rarely the people who use it most. A decision made in a leadership meeting lands on a form tutor at eight in the morning, and that gap is where most of the disappointment lives.

We build school management software, so here are the traps we watch for, including the ones that only appear in year two.

1. Buying school management software for the office and not the classroom

Finance, admissions and reporting features demo well because they are what leadership looks at. Attendance, behaviour notes and parent messages are what teachers touch daily. If the daily path takes six clicks, staff will keep their own spreadsheet, and then your central record is wrong in a way nobody notices for months.

2. Student data obligations arriving late

Who can see what, how long records are kept, what happens when a parent requests data, and where the servers sit are all decisions that shape the build. The United States Department of Education’s student privacy guidance is the clearest free summary, and it is far cheaper to read before procurement than after.

3. Treating school management software migration as an afterthought

Your existing data is messier than you think. Duplicate pupils, siblings recorded differently, historic staff who never left the system, and fields that were repurposed years ago by someone who has since retired. Ask for migration to be a named phase with its own time and its own sign-off, because otherwise it happens in the last fortnight and everyone discovers the problems live.

4. Ignoring what parents see

Parent-facing screens generate most of the support load, since there are far more parents than staff and they log in rarely. A confusing payment page or an unclear absence form turns into phone calls to the office, which is the opposite of what the system was bought to achieve.

5. Integrations promised rather than demonstrated

Your finance package, your learning platform, your door entry and your communications tool all need to talk to this. “We integrate with that” can mean a supported connector, or it can mean a nightly file export someone has to check. Ask which, and ask to see it running on another school’s setup.

6. School management software pricing that moves with you

Per-pupil pricing is reasonable and it compounds. Ask what happens when the roll grows, what a module costs to add later, what training costs after the first year, and what an export of your own data costs if you leave. That last one is the question suppliers least enjoy.

7. School management software without an internal owner

Someone on your staff has to own this, with time protected for it. Not a committee and not the supplier. Systems without an owner drift: permissions go stale, nobody retires old fields, and within two years the reports stop being trusted.

What a good procurement looks like

Shortlist school management software on the daily path rather than the feature list, and have two teachers and one office administrator run the same three real tasks on each system while you watch. Then ask each supplier the pricing questions above in writing. It is a slower process and it tends to produce a system people actually use.

School management software questions we are asked

How much does school management software cost?

Almost always per pupil per year, with modules priced separately, so the figure that matters is the total at your projected roll rather than the headline rate. Ask for a three-year cost including training and any charge for exporting your own data.

How long does school management software take to implement?

Plan a term, not a holiday. The build is rarely the constraint; data migration, permissions and training staff during a working week are, and schools that compress this into August usually spend September fixing it.

Can school management software replace every system we run?

Rarely, and trying is how procurements stall. Decide which two or three systems must be retired, integrate the rest, and revisit in a year.

The question to ask in year two

Whether the central record is still trusted. Good school management software makes the accurate path the quickest one, so staff have no reason to keep a copy. If departments have started keeping their own copies anyway, something in the daily path is too slow, and that is fixable while it is still a habit rather than a policy.

If you want to see how we have approached this, Acadmin is our own school administration product, and our custom software development page covers how we handle migrations and integrations.