Finlay.works
Calm, documented technology work—clear scope, written decisions, built to last.

Finlay.works

Calm, documented technology work—clear scope, written decisions, built to last.

Project-based custom software and IT services with written-first communication, clear scope, and documentation included.

Start with a written brief Services

Project-based. Documentation included.

Working style
  • Written-first communication 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.
Positioning

Calm, documented work. Clear scope. Written decisions. Maintainable outcomes.

Core offerings

Custom software development and IT services

Custom software and IT services focused on reliability and documentation, with clear scope, written decisions, and maintainable outcomes.

Custom software development

Purpose-built tools that reduce manual work and improve visibility.

  • Internal tools and workflows
  • System integrations and automation
  • Data cleanup, migration, and reporting
  • Lightweight web applications
  • Maintenance plans for long-term care

IT services

Practical support for devices, networks, and cloud systems.

  • Network setup and documentation
  • Email, storage, and backup configuration
  • Device setup and lifecycle planning
  • Access control and permission reviews
  • Vendor coordination and second opinions

Documentation and continuity

Written clarity so teams can operate without guesswork.

  • System diagrams and inventories
  • Runbooks and operating notes
  • Decision logs and change records
  • Security and access documentation
  • Handovers for new staff or vendors

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

    I return a clear scope statement, timeline, and estimate for approval.

  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

My values shape the way I 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, I 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

Written communication is preferred to reduce ambiguity and keep a clear record of decisions.

Email
joe@finlay.works

Typical response within two business days, in writing.

What to include
  • A short summary of the problem or goal.
  • What success looks like and who is impacted.
  • Known constraints: timeline, budget range, or compliance needs.
  • Any existing documentation and a description of current access (do not send passwords).