Obelra Book a scope call
Services

Four things, built properly.

Most software shops list twenty capabilities and are genuinely good at three. This is the whole list. If what you need isn't here, you'll hear that on the first call rather than three weeks into a project.

Custom websites

A site built out of your actual content and how you actually sell — not a purchased theme bent into shape until it nearly fits.

Typical duration3–4 weeks
Your time~1 hr / week
PricedFixed, after scoping

Signs this is what you need

  • You can't change the copy without worrying something will break.
  • You're paying monthly for a page builder and still can't get the layout you want.
  • It's slow on a phone, which is where most of your visitors are.
  • The site describes what you do, but never quite answers what people actually ask before calling.

What's included

Custom designContent you can edit Mobile-first buildPerformance budget Forms & notificationsAnalytics Search fundamentalsAccessibility basics
What you hold at the endThe code repository, hosting and domain in accounts registered to your business, CMS logins, and a recorded walkthrough of how to change things yourself.

Internal tools

The scheduling board, job tracker, or quoting calculator your team currently runs out of a shared file that only one person fully understands.

Typical duration5–9 weeks
Your time~1 hr / week
PricedFixed, after scoping

Signs this is what you need

  • One person is the only one who really understands the spreadsheet, and they take holidays.
  • The same information gets typed into two different places every day.
  • You can't answer "where does that job stand?" without asking someone.
  • The file has already broken once, and the fix was to make a copy.

What's included

Workflow modelled to your processRoles & permissions Import of your existing dataReporting views NotificationsChange history BackupsStaff walkthrough
What you hold at the endThe repository, the database, hosting under your business, written documentation of how the system is put together, and training for the people who'll use it daily.

SaaS platforms

Software other businesses pay to use — accounts, subscriptions, permissions and an admin side — built in phases you can stop between.

StructurePhased
First phaseWorking product
PricedFixed, per phase

Signs this is what you need

  • You've built something internally that other businesses keep asking about.
  • You know the problem intimately because you've lived it in your own operation.
  • You want to test whether people will pay before committing to a full build.
  • An existing product almost does it, but the gap is the part that matters most.

What's included

Multi-tenant from day oneSubscription billing Sign-up & authenticationAdmin console Usage reportingCustomer onboarding flow Email deliveryPhase-by-phase decision points
What you hold at the endEverything, at every phase boundary. Stop after phase one and you still own a working product and the infrastructure it runs on — not a half-finished dependency.

Integrations & automation

Getting the systems you already pay for to talk to each other, so nobody is moving data between two browser tabs by hand.

Typical duration2–5 weeks
Your time~2 hrs total
PricedFixed, after scoping

Signs this is what you need

  • Someone exports a file from one system every week and imports it into another.
  • Two systems hold the same customer and disagree about the details.
  • A job gets booked in one place and then re-entered somewhere else to be invoiced.
  • You've been told it's not possible, without being told why.

What's included

API connectionsFailure alerting Scheduled syncsWebhook handling Duplicate detectionReconciliation reporting Retry logicRunbook for what to do if it stops
What you hold at the endThe integration code, credentials held in your own accounts, and a written runbook — so a future developer can diagnose it without reverse-engineering anything.
Scope boundaries

What we don't take on

Knowing where a firm stops is more useful than another list of things it claims to do. For any of these we'll point you toward someone who specialises rather than stretch to cover it.

Ongoing IT supportHelpdesk, desktop support, and day-to-day user administration are a different discipline with a different rhythm. We build systems; we don't staff a support desk.
Hardware & networkingCabling, on-premise servers, phone systems and device procurement sit outside what we do.
Marketing retainersWe'll build a site that's fast and structured well for search, but we don't run ongoing SEO, ad campaigns, or content programmes.
Hourly staff augmentationWe take defined projects with a fixed price, not open-ended developer hours billed against someone else's backlog.
Unscoped rescue workInheriting a stalled codebase is possible, but never without a paid assessment first. Quoting a fixed price on code nobody has read isn't honest.
Work we'd be guessing atIf a project needs deep regulatory or domain expertise we don't hold, saying so early costs you a call instead of a quarter.

Not sure which of these it is?

Most people aren't, and it doesn't matter. Describe the problem and we'll tell you which category it falls into — or whether it needs building at all.

Book a scope call See how projects run