Finlay.works

Service management software, written plainly.

Finlay.works is focused on BareBones Ticketing: self-hosted service management software for teams that need controlled request intake, scoped workflows, audit posture, and predictable operations.

BareBones Ticketing. Fit assessments. Implementation support.

Delivery style
  • Communication in writing, with decisions recorded in plain language.
  • Clear scope boundaries before work begins and when changes are requested.
  • Documentation delivered with every project for long-term continuity.
Best first step

Send the problem, constraints, and desired outcome. The response comes back as written scope and practical next steps.

Product focus

BareBones Ticketing is the center of the business, with consulting used to help teams evaluate and adopt it well.

Written fit

The first step is a written assessment of service management needs, constraints, scope, and launch risk.

Adoption support

Implementation help stays close to workflow setup, documentation, access boundaries, and service desk handoff.

Choose a path

Find the right starting point quickly

Start with the service management decision in front of you: evaluate BareBones, scope implementation help, or request a written fit assessment.

Evaluating governed ticketing?

BareBones Ticketing is the flagship Finlay.works product for self-hosted service desk control.

View BareBones

Comparing service desk options?

Start with the operating problem: self-hosting, access scope, workflow control, evidence, and buyer readiness.

Read the buyer guide

Need implementation help?

Get scoped support for service management workflows, configuration, documentation, and narrow integrations.

Review implementation support

Product focus

BareBones Ticketing

Requests in a group mailbox and a tracking spreadsheet work — until someone has to show who approved what. BareBones Ticketing replaces that with structured intake, tickets that have owners, workflows you control, and evidence that builds itself, running on servers you own.

BareBones Ticketing agent queue showing lane signals and triage lanes BareBones Ticketing service catalog showing scoped service intake
Self-hosted control surface

Queue signals, access posture, workflow context, and audit-minded operations.

Related services

Service-management implementation support

Finlay.works helps teams evaluate, plan, configure, and document self-hosted service desk work around BareBones Ticketing.

BareBones fit assessment

Help deciding whether BareBones Ticketing fits the way your team handles service work.

  • Current request paths and ticketing pain
  • Self-hosting and operating constraints
  • Requester, agent, admin, and external participant needs
  • Workflow, SLA, approval, and audit questions
  • Clear proceed, pilot, defer, or fit-check recommendation

Implementation support

Help shaping the first useful operating path around BareBones.

  • Service catalog and intake structure
  • Workflow, status, and SLA configuration planning
  • Department-scoped access and role mapping
  • Launch checklist and operating handoff
  • Narrow import, integration, or reporting support when scoped

Documentation and continuity

Readable records so service teams can operate and hand off the system without guesswork.

  • Service desk operating notes
  • Requester, agent, and administrator guidance
  • Decision logs and change records
  • Access and support-boundary documentation
  • Handover notes for maintainers and future staff

How work runs

Structured, written, predictable

The process is designed to reduce human variability. Scope, decisions, and delivery notes are written and shared in plain language.

Scope boundaries
  • Projects are defined in writing before work starts.
  • Changes are reviewed and re-scoped before implementation.
  • No hidden recurring costs or surprise renewals.
  • Work begins only after scope and estimate are approved in writing.
  1. Written brief

    You send a short written brief with goals, constraints, and stakeholders.

  2. Scope and estimate

    We reply with written scope direction, useful questions, or a next-step estimate.

  3. Build and review

    Work proceeds in small, documented checkpoints with written updates.

  4. Handover

    You receive documentation, credentials, and a clean wrap-up summary.

Values

Values, practiced without pressure

Our values shape the way we work. The goal is honest service, careful stewardship, and respect for people—without pressure or manipulation.

If a request is unsafe, dishonest, or likely to cause harm, we will decline it plainly.

Read the full values statement
Honesty

Truthful estimates, transparent tradeoffs, and clear explanations even when the answer is no.

Stewardship

Responsible use of time, budget, and technology with long-term care in mind.

Care for people

Respect for users, teams, and stakeholders, including their limits and their time.

Integrity in delivery

Work that can be maintained, documented, and handed over with confidence.

Contact

Start with a written brief

Send the service management context once, in writing. A few paragraphs are enough to start a BareBones fit, service, proof, or procurement conversation.

Email
joe@finlay.works

Written email is the primary contact path.

What to include
  • How service requests, tickets, approvals, or handoffs work today.
  • Who needs a lane: requesters, agents, administrators, approvers, auditors, or outside participants.
  • Known constraints: self-hosting, timeline, budget range, workflow, access, audit, or compliance pressure.
  • Any existing documentation and a description of current systems (do not send passwords).