Services

Websites and workflows.
Built to fit.

For businesses that have outgrown disconnected pages, tools and manual work. Diagnose identifies what needs to change. Build puts the agreed solution in place.

One defined problem. The relevant website, workflow and tools.Diagnose, then decide. Build is a separate agreement.

Three ways to improve how the work gets done.

The diagnosis and your priorities set the scope. Each Build has a fixed price, agreed checks and a clear handover.

Website restructuring and redesign

If this sounds familiar: “Our site doesn’t say what we actually do any more.” “People can’t find the service they came for.”

You get
The agreed pages, organized around your customers and services, with accurate copy, a usable mobile experience and a tested inquiry route. An editing guide and handover explain how to maintain what we build.
What’s checked and what’s not included
Typical checks
Your services are described accurately, a test reader finds the right offer, the inquiry route works end to end, and you can make routine edits yourself.
Not included
Guaranteed leads or rankings, invented reviews or badges, or taking over disputed domains and accounts.

See a fictional demo: Northline Metal WorksA four-page site for a fabrication shop, with a quote form built around what an estimator needs.

Workflow and connected tools

If this sounds familiar: “Changes get lost between the office and the team.” “We enter the same thing three times.”

You get
One process mapped from a real job, then the agreed improvement: configure existing software, connect supported tools or build a tailored tool. We account for setup, ongoing costs, exceptions and who will maintain it. Your data stays yours and exportable.
What’s checked and what’s not included
Typical checks
The normal case, the missing-information case and the exception each behave as agreed, nothing happens without the approval you set, and your nominated team member can carry out the agreed routine tasks using the handover.
Not included
Connections we haven’t confirmed your plan allows, replacing software that works, or anything that sends, pays or decides on its own.

See a fictional demo: Change DeskA change-request tool for the same shop. Nothing reaches the floor until cost, date and confirmation are settled.

Practical AI inside one defined job

If this sounds familiar: “Staff keep asking the same questions.” “We want a first draft from our own records.”

You get
AI for one defined task, using approved business information and a named reviewer. For example, an assistant that prepares answers from your procedures and points to the supporting source for someone to check.
What’s checked and what’s not included
Typical checks
Test agreed examples, missing information and incorrect or misleading requests. Record unsupported answers and other failures, agree what is acceptable, and have your reviewer sign off before use.
Not included
Unreviewed customer messages, autonomous spending or promises of error-free output.

See a fictional demo: Inquiry DeskAn email assistant for the same shop. It fills the job record from the customer’s own words, flags what’s missing and drafts a reply for a person to approve.

Every Build: one fixed price before work starts, half to start and half when you accept it, and a 30-day fix period after that. Everything built is yours, with no subscription to us. Software, hosting, ads and tax are always shown separately before you agree.

First, a decision you can act on.

A paid Diagnose gives you the evidence, priorities and checks for one defined problem. This fictional example follows a job change through a service team.

DIAGNOSIS · EXAMPLEIllustrative, not a real client

The job changed.
The team needs the same version.

01

Two versions of the job are in use.

Evidence
ObservedIn this example, the office record shows the revised scope; the team’s handover still shows the earlier version.
Fix
Keep the approved scope in one shared job record and link the handover to it.
Measure
A test revision appears in the record the team actually uses.
02

The approval is separate from the work record.

Evidence
ObservedThe example approval is in an email, with no reference attached to the job.
Fix
Record who approved the change and link the confirmation before releasing it.
Measure
A change without the required approval stays on hold.
03

The same update is entered twice.

Evidence
AskedThe fictional owner describes copying each change into a second tool. The available integration has not been checked.
Fix
Confirm what the existing plans support before scoping a connection or custom tool.
Measure
The agreed normal case and exception case pass an end-to-end test.
?

UnknownHow often these handoffs need correcting.

Next step
Review a sample of recent jobs before estimating impact.
Reviewed by a person before delivery45-minute walkthroughBuild scope and price where feasible
  1. Prioritized for your situation

    The recommendation weighs likely impact, evidence, effort and dependencies.

  2. Evidence on every finding

    Observed, tested, or something you told us.

  3. Unknowns written down

    Unknowns and assumptions are labeled, with a next step to check them.

  4. A check for each change

    An acceptance check for the change, and an outcome measure where records are available.

  5. Yours to keep

    Whether or not you hire Eren to build.

An illustration of the format. Yours will be specific to your business.

It starts with a free First Look. The $750 Diagnose and a fixed-price Build are separate, and you can stop after either. See pricing

Start here

Start with a free First Look.

Bring one website or workflow question. We’ll establish whether Eren is a fit and what a useful next step would be.

  • Free · about 15 minutes
  • Request first; we arrange the call with you
  • Paid work starts only by agreement