Philosophy

Philosophy

IT × ∞ ― more room to act.

Our name, Preferred, means the option people would rather choose. Staying the most preferable choice — for clients, and for the people who use what we build — is where Preferred Inc. starts.

IT doesn’t fix everything. Used with a clear purpose, though, it expands what’s within reach. We build software and also run a café, an e-commerce brand, and a real estate business — standing on both the build side and the use side keeps our proposals grounded.

Mission

Create our own businesses, and give back.

We start businesses ourselves, and feed what we learn back into client work. That is the job.

Many IT shops only build for others. We also run Slow Rush Coffee in Kamakura, LC COFFEE e-commerce, and Preferred Estate in Shinjuku — inventory, customer service, logistics, decisions under uncertainty included.

What breaks in our own ops shows up in how we scope and build for clients. Create, learn, return — a simple loop.

Vision

Right-sized IT, in every workplace.

Not oversized, not underpowered. Systems that still run next month, within reach of companies of any size — that is the future we are working toward.

We get there by turning vague “we should do something with IT” into work scoped to what each workplace actually prefers — one project at a time.

Values

Our Values

Four rules of thumb for how we design work and talk with clients.

Value 01

Operator’s view

We run businesses ourselves

We build systems, and we use them. Running a café in Kamakura and a real estate business in Shinjuku keeps us honest about day-to-day constraints — not only specs on a slide.

Value 02

Same team

From scope to operations

Requirements, design, build, test, and operations stay with one team. Fewer vendor handoffs mean intent is less likely to erode mid-project.

Value 03

Security with rules

ISMS (ISO 27001)

We hold ISO 27001 / ISMS certification. How client data is handled is written down — not left to individual habit.

Value 04

Right-sized scope

Start where it helps

We don’t push one framework onto every project. Scope follows the problem, the team, and the budget — small when small is enough.