RAINS / IT CONSULTING

From the IT decisionto a usable delivery.

RAINS is an IT consulting company for teams that need to make the work clear before they change a system. Four focused desks cover advisory, automation, narrow operational work, and self-serve handover tools.

Sort the question in 3 steps See all four desks

Advisory
Automation
Fixed-scope work
Consumer tools

FOUR BUSINESS LINES

Choose by the job you need to move next.

Each desk has a different customer and deliverable. The same product is not repeated under another name.

RAINS / 01

RAINS Advisory

For companies

Decide what to change—and what not to change.

IT strategy, small-office networks, SaaS operations, identity lifecycle, vendor proposals, and handover design. Start read-only and leave a decision memo or runbook.

Network review / lifecycle design / IT handover

See RAINS Advisory

RAINS / 02

Automation Note

For companies and agencies

Put an automation boundary in writing before the build.

n8n and Make feasibility review, stabilization, paid pilots, implementation, and agency overflow support. The dedicated site owns the offer and pricing.

Feasibility review / pilot / implementation

Open Automation Note

RAINS / 03

Narrow Works

For recurring back-office work

Take one repeated check out of a wider system project.

A fixed-scope line for small, deterministic operational work. The first validation offer compares two redacted CSV files and leaves a reviewable difference report.

Narrow Diff Review / local-first / fixed scope

See Narrow Works

RAINS / 04

引き継ぎ設計室

For individuals and small teams

Start the handover yourself with a usable sheet.

Free guides, spreadsheets, and paid kits for a resignation, transfer, or owner change. No consulting engagement is required to begin.

Free guides / Excel templates / execution kits

Open Hikitsugi Design Room

NOT SURE WHERE TO START?

Name the situation. The desk follows.

“We need an independent IT view.”: RAINS Advisory
“We need an n8n or Make workflow.”: Automation Note
“We repeat one comparison every month.”: Narrow Works
“I want to prepare a handover myself.”: Hikitsugi Design Room

ONE OPERATING MODEL

Evidence first. Access later.

01
Set one question
Name the decision, owner, deadline, and material that already exists.
02
Write the boundary
State what is included, excluded, and accepted before access or payment.
03
Leave a usable artifact
Deliver a memo, report, workflow, or template someone else can review.

WHAT A DELIVERY LOOKS LIKE

A decision should not disappear into a slide deck.

The fictional row below shows the minimum information a handover needs.

Current material	Owner	Due	Next check
Office plan	Move lead	Before vendor meeting	Mark unanswered network questions

Illustrative row / no client data

Read the fictional delivery sample

INFORMATION BOUNDARY

The first contact is about the work—not your secrets.

These rules apply across all four desks.

Do not send: Passwords, MFA codes, private keys, personal data, customer names, or production exports.
We do not imply: Unverified results, guaranteed ROI, guaranteed security, or a client case that does not exist.
One responsible desk: Each offer, price, event, and contract has one responsible desk.

START WITH RAINS ADVISORY

Bring one IT decision that keeps stopping.

The situation, systems, and deadline are enough. The three-step check runs in your browser and sends nothing.

Sort the question in 3 steps Email a prepared brief