Taking on 1 client from January Lisbon 18:20 · Toronto 13:20 Reply within one business day
Email us

Contact/One conversation, no sequence

Tell us the number on your cloud bill.

That single figure tells us more than a requirements document. Add one thing that keeps breaking, and we can usually say within a day whether we're useful to you.

Send a message

The form opens your email client with the details filled in — there's no server behind it, which is also why we can promise we don't store anything.

Prefer to skip the form? Write to hello@nimbusworks.chenky.sbs directly. Either way, a human replies.

Or just email

  • Email hello@nimbusworks.chenky.sbs
    Goes to both of us. No ticket system.
  • Response Within one business day. Usually same day if it arrives before 16:00 Lisbon.
    If you don't hear back in two days, it went to spam — try again.
  • Lisbon Iris · UTC+0 (WET) / UTC+1 (WEST, Apr–Oct)
    Working hours 09:00–18:00
  • Toronto Nathan · UTC−5 (EST) / UTC−4 (EDT)
    Working hours 08:30–17:30
  • Overlap 14:00–18:00 Lisbon = 09:00–13:00 Toronto
    That's the window for calls with both of us.
Scheduling

We don't use a booking widget. Reply with two or three windows that work and we'll confirm one — it's faster than it sounds, and it means the call is with an engineer rather than a calendar.

01

What happens after you send it

Three steps, no discovery sequence, no automated nurture emails.

  • Step 1 · Day 1 A short reply from Iris or Nathan, usually with two questions and an honest first impression: "this sounds like a review" or "you probably don't need us".
  • Step 2 · Day 2–5 A 30-minute call. Screen shared, no slides. Bring the bill and one architecture diagram, even a bad one — bad diagrams are more informative than tidy ones.
  • Step 3 · Day 5–7 A one-page scope note with a fixed fee, a start date and a delivery date. If it's not right, tell us and we'll change it before anything is signed.

Helpful to include

  • Monthly spend, and roughly how it's split
  • Team size, and how many people can touch production
  • The last incident that actually hurt, and how long it lasted
  • Any deadline that isn't negotiable (audit, migration, funding round)

Not necessary

  • An NDA before the first call — we'll sign one, but it can wait
  • A polished deck
  • Access to anything. Read-only comes later, and only if we scope work
  • A budget range. We'll ask, and "we don't know yet" is a valid answer

Not ready to talk? The audit page has the details.

Fixed fee, two weeks, and a written answer you can forward to whoever signs off on it.

See pricing