title: A Day for a Problem
description: Focused Day - one problem, one working day, EUR 1,000. A fix, a design, an investigation, or a decision. Fixed scope, fixed price.

# A Day for a Problem

*Focused Day - EUR 1,000*

One problem. One working day. Something useful at the end.

The work can be a fix, a design, an investigation, a deployment, or a decision. We agree on the boundary before kickoff and spend the day solving it. No vague "discovery phase" that quietly turns into a month.

## Good fits

- Diagnose and fix one production or deployment problem
- Review one risky architecture decision and leave a written recommendation
- Add one bounded CI/CD, auth, data, or observability improvement
- Turn a fuzzy feature into a buildable design with acceptance criteria
- Run a timeboxed technical spike and make the build / do-not-build call
- Inspect a codebase around one named concern and produce a remediation plan

The day is deliberately narrow. "Review our platform" is not a scope. "Find why every deployment is different and leave us with a deterministic build" might be.

## What you receive

- The code, configuration, document, or decision we agreed to
- A short handoff: what changed, what remains, and what I would do next
- Receipts - commits, commands, measurements, or source links where they matter
- A 30-minute walkthrough if the result needs one

If the answer is "do not build this", that is a valid result. Expensive work avoided is still work done.

## How it runs

1. A short call or written exchange to make sure the problem fits inside a day.
2. I send the access checklist and invoice.
3. One working day, focused on the agreed problem.
4. Handoff at the end of the day or the next business morning.

Access delays can spread the work across the calendar. They do not expand the scope.

**Payment:** EUR 1,000 at kickoff.

## What this is not

- A generic audit
- A sales call in disguise
- A day of backlog execution
- A promise to repair an entire system for EUR 1,000
- A cheap opening bid for a clearly larger project

If the problem turns out bigger than a day, you still get the day's result - and a straight answer about what the rest would take.

Send me the one problem you want gone: [tinmarkoviccs@gmail.com](mailto:tinmarkoviccs@gmail.com?subject=Focused%20Day)

<p style="margin: var(--space-8) 0;">
  <a class="btn-primary" href="/contact" data-open-booking>Or book a call</a>
</p>

<p><a class="secondary-link" href="/work">How longer projects run →</a></p>