Our Blog
Insights, Ideas and Digital Trends
Written by the people who build the systems, not by a content schedule. Working notes on web development, mobile applications, AI automation, cloud and server management, and digital marketing, from projects where these decisions actually had to be made.
Latest Blog Articles
Stay updated with expert insights, how-to guides, industry trends and technology news.
-
What Makes a Software Project Fail in the First Year
Most systems do not fail in the first month, they fail in month eight, and the causes are boring and repeatable: nobody owns the outcome, the specification describes a process that has since changed, the common case takes too many clicks, unrecorded shortcuts have compounded, and the knowledge left with the people who…
Grace Wilson
Read More
-
The Difference Between a Website Owner and a Website Maintainer
Ownership and maintenance are two different jobs that often get one job title, and the queue always wins because it is urgent while judgement is not. This explains what an owner actually decides, what a maintainer actually patches, why content accuracy decays quietly, and which questions to ask your team to find out…
Ella Thompson
Read More
-
How to Read a Development Proposal
A proposal is a comprehension test, a plan, and a contract stacked together, and clients read it in the wrong order. Read the restatement of your problem first, then look hard at what the scope leaves out, then at who is accountable for each phase, then at the commercial terms and the clauses written to protect the…
Isla Fraser
Read More
-
Questions to Ask Before Hiring a Development Team
Vetting a development supplier means working out who will actually write the code, what assumptions sit behind the price, and who answers the phone when something breaks at midnight. Isla Fraser
Read More
-
Preparing a Technical Specification Before You Commission a Build
The single biggest factor in project cost is how well the requirements were understood before writing started. Isla Fraser
Read More
About the Insights archive
Who writes here, what the articles are based on, and how to reach us about any of them.
Each one carries an individual byline and a short editorial profile, so you can see who wrote it and what they cover before you read it. The profiles are editorial identities maintained for this publication rather than personal pages, and the article itself always names its writer at the foot of the page.
Regularly, and on no fixed schedule. The articles here are written because there is a question worth answering rather than to fill a calendar, which means the gaps are as variable as the subjects.
Not without asking. These are written for SmartEdge IT Solutions and are protected, so if you want to quote one, link to it, or reuse it in a briefing, get in touch first and we will almost always say yes to a link.
They are composites drawn from the kinds of problems we are asked about, written so they are useful rather than flattering. Where an article describes a specific decision, the reasoning is the reasoning we would give you. Nothing here claims a client, a result or a figure that we cannot show evidence for.
Only to explain a decision not to use it. The technology and innovation page sets out what is in the stack here and what each platform is actually used for.
Often, yes. Send the question through the contact form and it will be treated as a candidate for the archive rather than a support ticket, if it is a question other people are also asking.
There is not one set up yet, and we would rather not describe a mailing list that does not exist. If you want to follow the archive, the contact page is the place to say so; if enough people ask, it becomes a reasonable thing to build.
Of course. Take whatever is useful, and if you then want it built, the services overview explains the shapes of work we take on.
STAY UP TO DATE
Need Guidance on Your Next Digital Step?
Most of the questions that lead someone here are not really about technology. They are about whether a project is worth doing, what it will cost, and what it will demand of the team afterwards. Bring the situation rather than a brief. We will tell you what we would do, what we would deliberately not do, and roughly what it takes.