The bigger the project,
the first thing to settle is not the price but the requirements.
Sites that span multiple departments. Sites wired into core systems. Renewals whose requirements are not yet settled. Webharu takes these on phase by phase, starting from requirements definition. The first meeting and a rough range cost nothing.
How we work — turning the estimate into a deliverable.
A total quoted before the requirements are settled carries a risk premium sized to the uncertainty. That is why Webharu does not promise a total up front on large projects. You invest a small amount in requirements definition first, and we hand you a figure with no premium attached, as a deliverable.
- 1
Free consultationFree
We ask about your current situation, your goals and the departments involved, then give you the shape of the project and a rough range on the spot. The company brochure for your internal approval can be handed over at this stage too.
- 2
Requirements Definition and Research Phase¥500,000and up (excl. tax)
About one to one and a half months. We survey your current site, your data and your workflows, then hand overa requirements document, a site structure plan and an accurate estimate for the build itselfas the deliverables. They are yours — they also give you what you need to decide whether to take the build elsewhere.
- 3
The estimate for the buildA requirements-definition deliverable
A firm quote based on the requirements definition. We never change the figure once work has started. Staged launches and phased delivery are proposed here as well.
- 4
Design, build and launch
Progress is made visible through regular meetings and reports. After launch, our own operations platform and SLA-backed maintenance cover updates and incident response.
A guide to the cost.
This is the lower guide figure from our large-scale projects to date. The firm number is presented as a deliverable of the Requirements Definition Phase (¥500,000and up) — a total quoted before the requirements are settled carries a risk premium sized to the uncertainty, so we do not promise one in advance.
Payment models — lump sum, or SaaS-style.
Alongside the conventional lump-sum contract (a one-time purchase with the code delivered), we offer a SaaS-style contract of a setup fee plus a monthly license fee. Choose whichever fits how your budget is structured and how your procurement rules work.
Setup fee plus monthly license fee
You can start without budgeting a large upfront investment, on a simple contract with just two lines: setup and migration, and a monthly license fee. The monthly fee is designed to cover not only maintenance but ongoing improvements to your existing content.
A flat monthly rate, from launch day
Contract terms are 12, 24 or 36 months. The monthly rate stays flat for the term, and billing starts on the launch date (during the build, only the setup fee applies).
Your data can leave at any time
Content export is guaranteed in the contract. This SaaS model exists to fit your procurement and budgeting, not to lock you in.
* Figures and contract terms are proposed individually according to the requirements. We can also explain which model suits you in a free consultation.
We fit your procurement process as it stands.
Internal approval and review
A single document covering our company, our work, how we work and a rough range — sent for nothing more than your email address. Use it from the comparison stage onwards.
Security and legal
NDAs signed, security check sheets completed. Third-party measurements: SSL Labs A+ / Mozilla Observatory A+ (measured on our own site).
Contracts and payment
Invoice payment (bank transfer) and phase-by-phase split contracts. We sign an individual contract, and the figure does not change once work has started.
Multilingual and overseas offices
Multilingual rollouts in English, Korean and other languages, and sites for overseas offices. JTB Americas is among our work.
Frequently asked questions.
Can we commission just the Requirements Definition Phase?
Yes. The deliverables — the requirements document, the site structure plan and the estimate — belong to you, so you are free to commission the build itself from another company. If you do continue with us, the estimate for the build will not change from what the requirements definition set out. And if you decide to stop at the end of the phase, no further contractual obligation arises.
Why don’t you give a total figure up front?
A total quoted before the requirements are settled carries a risk premium sized to the uncertainty. By investing a small amount in requirements definition first, we can give you an accurate figure with no premium attached — and in most cases the total comes down as a result. Consultations and rough ranges are free.
Can you take part in pitches or competitive bids?
Consultations, rough ranges and our company brochure are all free. Concrete proposals that involve site structure or design work are taken on as the Requirements Definition Phase, which is paid.
You are based in Sendai — can you handle projects in Tokyo?
Yes. Meetings are mostly online, and we visit in person when it helps. We have also built a site for an overseas office (JTB Americas).
Can you complete our security requirement check sheets?
We do. Under an NDA, we answer with our architecture, how data is handled, and third-party measurements (SSL Labs A+ / Mozilla Observatory A+) attached.
Can we sign a monthly contract instead of a lump-sum one?
Yes. We offer a SaaS-style contract of a setup fee plus a monthly license fee (12, 24 or 36 months, a flat monthly rate, billing starting on the launch date). The monthly fee covers maintenance and ongoing improvements to existing content, and data export is guaranteed in the contract. We propose the detailed terms case by case.
Start by telling us the shape of the project.
Consultations and rough ranges are free. Starting at a stage where an NDA is needed is no problem.
Come as you are, even if the requirements are not settled. Settling them is where our work begins.