opsform.
About OpsForm

Girgis Ramzi builds operational software in Brighton.

OpsForm is his trading name. He is a UK sole trader based in Brighton, and he is the person who does the work: practical web applications and automation for teams that have outgrown spreadsheets, manual workarounds and almost-right tools.

Who does the work

The person behind the name.

Girgis Ramzi trades as OpsForm. It is not a limited company. He is the person who maps the workflow and builds the software.

That work is custom web applications, internal systems, booking systems, portals, dashboards, spreadsheet replacement, workflow automation and the integrations that stop people copying information between tools.

One approved client comment

Brighton Flyway Transport, a South East transport operator, approved a comment about moving off spreadsheets onto a portal built around their operation. It is published on the Work page.

The transport and property demonstrations on that page use sample data. They are not his case studies, and they are not Brighton Flyway Transport’s system.

Read the approved comment →
The product principle

Practical before flashy.

A successful business system should make the next action obvious, reduce duplicate work and give staff one dependable source of truth—not another brochure website.

That means understanding the process before writing code, keeping the first release focused and designing a foundation that can grow.

“The goal is not more software. It is fewer manual steps, fewer errors and one place your team can trust.”

OpsForm product principle
How OpsForm approaches a build

Operational clarity

Statuses, responsibilities and next actions should be explicit rather than scattered across inboxes and spreadsheets.

Traceability

Important actions should leave a useful history so staff can see what changed and why.

Maintainability

The system should be understandable, deployable and supportable after the first launch.

Security by design

Permissions, validation, secrets and production configuration are part of the product rather than a final polish step.

Automation with visibility

Automated actions should reduce admin without making outcomes impossible to explain.

Focused releases

Build the smallest coherent version that creates real value, then improve from usage.

Good project fit

OpsForm is strongest when the workflow matters.

Your team has repeatable operational work.
The process contains rules, handoffs or approvals.
You want one source of truth instead of disconnected tools.
You can nominate a decision-maker who knows the workflow.
You value maintainability and clear scope over a rushed prototype that cannot be operated.
Honest fit

When OpsForm probably isn’t the right fit.

We would rather point you towards a better option than take on work that a custom operational build is not suited to. It is usually not the right fit if:

You mainly need a brochure or marketing website rather than an operational system.
A standard off-the-shelf product already fits the workflow and only needs configuration.
A native iOS or Android app is the core product, rather than a responsive web application.
A fixed deadline leaves no room for discovery, testing or a sensible first release.
The priority is the lowest possible price rather than software your team can operate and maintain.

Have a process that has outgrown the tools?

Start by describing what happens today.

Start a conversation →