Code editor and analytics dashboards on monitors in a dark room

IT services

Software and web portals, built by people who run them

Software publishing, marketplace and listing portals, integrations and long-term maintenance — a separate practice, with the same standard of documentation.

What we deliver

Four ways we work on software

Software publishing

We publish and license software built for the way operational businesses actually run. Stock management, pricing intelligence, reconditioning workflows and customer follow-up live in one place, so a small team can handle a large volume of work without spreadsheets holding everything together.

Releases are incremental and documented. Every licence includes onboarding, data import and a support channel staffed by people who understand both the code and the operation it describes.

  • Stock, pricing and workflow tools
  • Licensing, onboarding and data migration
  • Regular releases with clear change notes
  • Direct support from the people who build it

Web portals

We design, build, host and operate marketplaces and listing portals end to end. That covers search and filtering, media handling, lead capture and routing, feed ingestion, analytics and the day-to-day operational work that keeps a portal healthy long after launch.

Performance and accessibility are treated as requirements rather than extras. Portals are built to load fast on a weak phone signal, to be readable by screen readers, and to stay indexable so listings are found by the people searching for them.

  • Marketplace and listing portal builds
  • Feed ingestion and third-party integrations
  • Hosting, monitoring and maintenance
  • Search, SEO and performance engineering

Integrations & data work

Most systems fail at the seams. We connect the tools a business already pays for — inventory, finance, messaging, analytics, third-party feeds — and make the data move on a schedule instead of by copy and paste.

Data stays exportable and owned by the client. Schemas are documented, transformations are reviewable, and nothing depends on a single undocumented script.

  • API and feed integrations
  • Scheduled imports and exports
  • Reporting and analytics pipelines
  • Documented, portable data models

Product & maintenance retainers

Software is not finished at launch. A retainer keeps someone accountable for uptime, dependency updates, small improvements and the questions that come up once real users arrive.

We prefer small, frequent changes with clear notes over long silent rewrites. You always know what shipped, what is next and what it cost.

  • Uptime monitoring and incident response
  • Dependency and security updates
  • Prioritised backlog with short cycles
  • Transparent, predictable billing
Stock and pricing dashboard displayed on a monitor

How we build

Practical software, documented as it goes

Built from real use

Our tools began as an internal answer to a practical problem: knowing exactly what we hold, what it cost, what it needs and what it should sell for. Because we still use them daily, features exist because a real workflow needed them.

Plain interfaces

Screens are designed for people working quickly, often on a phone and often with dirty hands. Fewer options, larger targets, no decorative complexity.

No lock-in

Data is exportable, formats are documented and hosting can be moved. A client who wants to leave should be able to, which is a healthier reason for them to stay.

Small increments

We ship in short cycles, watch how the tools are actually used, and remove friction rather than adding features nobody asked for.

How it works

From first conversation to running software

Nothing moves to the next stage until the previous one is written down and agreed. It keeps estimates honest and removes most of the surprises that make software projects unpleasant.

  1. 01

    Discovery

    A short, focused conversation about the workflow, the volumes involved and what currently breaks. We write back what we heard before anything is quoted.

  2. 02

    Scope and estimate

    A written scope with a fixed first milestone. Assumptions and exclusions are listed openly, so there is nothing to discover later.

  3. 03

    Build in cycles

    Working software in short cycles, reviewable as it goes. Feedback changes the next cycle rather than being stored up for the end.

  4. 04

    Launch and care

    Deployment, monitoring, handover documentation and an agreed support arrangement — with the same people who built it.

Questions

Asked often

If your situation is not covered here, describe it to us — we would rather answer once, clearly.

Do you only build software for the motor trade?

That is where our tools began, but the patterns — inventory, condition data, pricing, lead handling — apply to plenty of other operational businesses, and we build for those too.

Can we license your existing software instead of a custom build?

Often the fastest route. We license the published product, migrate your data and configure it around your process, and only build custom pieces where the standard product genuinely does not fit.

Do you host what you build?

Yes. Hosting, monitoring and maintenance can be included, or we can deploy into infrastructure you already own and hand over the documentation.

How do you handle our data?

Only what the system needs, stored in documented schemas, exportable at any time. Access is limited to the people working on your project.

Contact

Describe the project

A licence, a portal build, an integration or ongoing maintenance — send the details and we reply within one working day.

Company
Bright Frame Pal Limited
Email
tech@brightframepal.com
Hours
Mon–Fri 09:00–18:00