Build — technology and systems
What we usually find
It works, until two people need it at once, or the person who built it is unavailable, or a formula silently breaks.
Generic tools force the operation to work the vendor’s way, and the gap gets filled with manual steps nobody documented.
Systems that do not talk to each other convert staff time into reconciliation work that produces nothing.
Numbers arrive late, cost hours to produce, and are usually already out of date when a decision is made on them.
Approach
The first stage is not technical. It is establishing where information enters the business, who needs it, where it stalls and what a delay actually costs. That is what determines whether the answer is a platform, a small internal tool, or a change to the process that needs no software at all.
The smallest system that removes the constraint is almost always the right one. Scope that grows before the first version ships is the most reliable predictor of a project that never does.
Web
A corporate site is a commercial instrument: it has to load quickly, say what the business does, and make the next step obvious. Performance, accessibility and search architecture are handled as part of the build rather than as a later clean-up.
For eCommerce that extends to the parts that only matter once real volume arrives — checkout behaviour under load, payment integration, tax and invoicing, and reconciliation that does not depend on someone exporting a spreadsheet.
Built for speed, clarity and search.
Storefront, checkout, payment and fulfilment integration.
Customer-facing tools that are part of the product.
Internal systems
Booking systems, operational dashboards, approval flows, inventory, reporting — the tools that decide how much work a team can absorb before something starts to slip.
These are built with roles and permissions from the start, because "everyone can see everything" is the design decision that becomes impossible to unwind once the team grows.
Custom systems built around an existing process.
Availability, reservations and the reporting behind them.
The numbers that drive decisions, produced automatically.
Connecting systems that were never designed to meet.
Automation and AI
Automation is scoped against the hours a process currently costs. If a task takes twenty minutes a week, automating it is a hobby. If it takes two days a month and blocks something else, it is an investment with a calculable return.
The same test applies to AI. It is useful for classification, drafting, summarising and extracting structure from unstructured input. It is not useful as a feature added so the product can claim to have one, and it is not appropriate anywhere an incorrect answer carries real cost without a human check in the path.
Afterwards
Everything is built on stable, widely supported technology, documented, and delivered with access to the accounts and infrastructure that run it. If we stop working together, you own a system another engineer can pick up.
Ongoing maintenance is available, but it is a choice rather than a dependency created by the way the thing was built.
Capabilities
How to engage
A short paid engagement that produces a technical plan, scope and estimate before any commitment to a build.
Priced on scope
Delivery: Typically 1–2 weeks from kick-off.
Design and development of a corporate site, eCommerce store or marketing platform.
Priced on scope
Delivery: Delivered in stages against a timeline agreed in the proposal.
A custom internal system — booking, operations, reporting or management — built around an existing process.
Priced on scope
Delivery: Delivered in stages with review points, against a timeline agreed in the proposal.
Targeted work that removes a specific piece of manual process, scoped against the hours it currently costs.
Priced on scope
Delivery: Scoped and scheduled in the proposal.
Ongoing hosting, updates, monitoring and development capacity under a monthly agreement.
Priced on scope, billed monthly
Delivery: Monthly, ongoing. Either party may end the arrangement with 30 days’ notice.
Questions
Whichever costs less to live with. Replacing a system that works is rarely justified; connecting it to the thing it should have been talking to usually is. That assessment happens during discovery, before any commitment to a build.
Something not covered here? Ask directly.
If you know what you want built, send the brief. If the problem is still taking shape, a short call is the faster route. Either way you speak directly to the person doing the work.
Or email directly: hello@perspektivagroup.com