Brand
Guidelines v2.0

The official visual identity system for edamame — the Kintone partner in the Philippines. Codifies the layout grammar and pod-coherent patterns introduced in April 2026.

What's new in v2.0

v2.0 · April 2026
01 — Logo

The edamame mark.

Our logo combines a pod icon with the "edamame" wordmark. The pod holds three beans — the center bean is gold, representing the core value we deliver. The sides are green, representing growth. The whole mark is the company's design grammar.

edamame
edamame

Logo rules

Wordmark case
Always lowercase
"edamame" — never "Edamame" or "EDAMAME"
Legal entity
Edamame Inc.
Use in copyright, contracts, invoices only
Clear space
1× bean height
Minimum clear space around the full logo
Minimum size
120px wide
Full logo with wordmark. Icon alone: 24px
Center bean
Always gold
#C4A35A — never change the center bean color
Three beans
Never two, never four
The three-bean structure is canonical. Preserved across all uses.

Icon variants

Light background
Dark background
App icon
Favicon / small
02 — Color

Color system.

A grounded, natural palette anchored by forest green and warm gold. Kintone red is reserved exclusively for CTA buttons — never text, never decoration.

Primary — Growth & identity

Forest Green
#4A7C59
Primary brand color. Nav accents, ghost buttons, links, small dot markers, side beans.
Light Green
#6B9B7A
Hover states, dark-background logo beans, soft data visualizations.
Dark Green
#3A6349
Footer, hero gradients, deep emphasis.

Accent — Core value

Warm Gold
#C4A35A
Center bean, premium tier, badges, highlights, "live" indicators, data accent markers.
Light Gold
#E8D5A3
Subtle gold backgrounds, highlighter pass under accent words.

Action — CTA only

Kintone Red
#ED1C24
CTA buttons ONLY. Never for text, links, icons, or decoration.
Light Red
#FF5A5F
Gradient end for primary CTAs. Also "live" pulse indicator in data panels.

Neutrals & surfaces

Forest
#0a1e15
Hero gradients start, deepest background.
Ink
#1A1A18
Footer background, live panels, darkest text.
Text
#2D2D2A
Body text, headings on light backgrounds.
Muted
#6B6B66
Secondary text, captions, labels, metadata.
Off-White
#FAFAF8
Page background, card backgrounds.
Cream
#F0EDE8
Alternating sections, tag backgrounds, warm contrast.
03 — Typography

Type system.

Two display/body faces for English, one for Japanese, one for data. DM Serif Display for editorial impact. DM Sans for body & UI. Noto Sans JP for Japanese. JetBrains Mono for numbers, labels, and technical specs.

Display · DM Serif Display
Kintone, engineered.

Hero headlines, section titles, statistics, pull quotes. Italic variant for accent words inside a headline. Never for body text. Use sparingly for maximum editorial impact.

Body & UI · DM Sans
We don't pitch AI. We run on it.

Paragraph body text. A small firm in Pasig serving 2,400+ users across fifty enterprise clients — including ORIX Metro, Daikin, and Quipper.

Paragraphs, navigation, buttons, labels, captions. Weights: 400 body, 500 emphasis, 600 labels/nav/buttons, 700 headings. Italic 400 reserved for voice moments.

Japanese · Noto Sans JP
Kintoneを、自ら使う側が設計する。

日本語本文。パシグに拠点を置く小さな会社が、50社のエンタープライズ顧客で2,400名以上のユーザーを支えています。

All Japanese text, body & display. Line-height 1.8 for readability. Pairs with DM Sans for mixed EN/JP UI. Never use "type-sample type-sample--mono"> Data & labels · JetBrains Mono

2,443 users · ₱1.87M/mo · $18/mo

№ 01 · DEPLOYMENT · 2026-04-20

New in v2.0. Stats, live data values, section numbers (№ 01/02/03), uppercase labels, timestamps, technical metadata. Sizes 10-14px for labels, 22-28px for hero data values. Weights 400-600.

Type scale

UseFaceSizeWeight
Hero headlineDM Serif Displayclamp(44px, 7vw, 88px)400
Section titleDM Serif Displayclamp(32px, 5vw, 54px)400
Subsection / card titleDM Serif Display22-28px400
Lede / sub-headlineDM Serif Display italic18-22px400 italic
Body paragraphDM Sans15-17px400
Nav links / buttonsDM Sans13-14px500-600
Section number (№ 01)JetBrains Mono11-12px500
Uppercase label / tagJetBrains Mono10-11px (0.18-0.24em tracking)500-600
Data value — heroDM Serif Display28-40px400
Data value — inlineJetBrains Mono or Serif14-22px400-500
JA bodyNoto Sans JP15-17px (line-height 1.8)400
04 — Voice

How we sound.

We write like a sharp consultant who respects your time — direct, specific, and grounded in Philippine business reality.

✓ We are

Direct. "Kintone starts from ₱1,000/user/month." Not "pricing varies based on your needs."

Specific. We name competitors, show real peso amounts, cite actual deployment timelines.

Honest. We say when Kintone isn't the right fit. We compare fairly.

Local. Philippine pesos, Philippine business context, Philippine internet reality.

✗ We never

Hedge. "We believe we can potentially help transform..." → Just say what we do.

Buzzword. "Synergize your digital ecosystem" → "Build the apps your team actually needs."

Oversell. We position Kintone as one strong option among many — more credible, converts better.

Ignore context. No generic SaaS copy. Everything connects to PH business reality.

Language rules

ContextUse
Brand name in copyedamame (always lowercase)
Legal / contracts / copyrightEdamame Inc. (formal entity name)
Sentence-start brand mentionRestructure: "Our team provides…" not ". edamame provides…"
English body textConversational, PH-market specific. DM Sans.
Japanese body textNative-level business Japanese. No unnecessary katakana. Noto Sans JP.
JA CTA textAction-oriented: "無料で相談する" not "コンサルテーションを予約する"
PricingAlways PHP: "₱1,000/user/month (5-user minimum)"
Stats in copyJetBrains Mono inline for exact figures: 2,443 users, ₱1.87M/mo
Bylines"By Tom Arai, edamame"
Section numbers№ 01, № 02, № 03 (not "Section 1" or "Part One")
05 — Layout modes · NEW

Three layout modes.

Every page on edamame-jp.com uses one of three sanctioned layout modes. Each expresses the brand differently. Pick the one that matches the content's purpose — never invent a fourth.

MODE № 01
Field Notes
Editorial documentary.
Magazine masthead. Numbered sections (№ 01/02/03). Pod-curve dividers between sections. DM Serif Display-heavy. Cream dominant. Field-note style blog cards with tags. Feels like a Japanese business quarterly.
Use for Long-form content pages, case studies, About, Values, editorial landing pages, blog index.
MODE № 02 · ANCHOR
Data Atelier
Proof-first editorial.
Graph-paper hero background. Live data panel with real numbers. Gantt-style client tenure. Ink-on-gold comparison spec sheets. Filterable knowledge base. Numbers everywhere — always typeset in JetBrains Mono or Serif, never Sans.
Use for Homepage, deployments/customers page, ROI calculator, pricing transparency pages. Any page where proof & data drive conversion.
MODE № 03
Pod & Bean
Mark-driven, organic.
Asymmetric pod-shaped corner radius on every card. Three-bean structure for any service/product grouping (left-green, center-gold = premium, right-green). Floating pod-silhouette decorations. Dot markers everywhere, never bullets.
Use for Product pages, service overview, KinPlug landing pages, special campaign pages, partnership announcements.

Within one page, stick to a single mode. Never blend. Exception: Data Atelier may borrow Pod & Bean's three-card pricing tier layout (pod-shaped radii) as its final section.

06 — Pod motifs · NEW

Pod-coherent patterns.

Design elements that echo the logo's geometry. Use these to make any page feel unmistakably edamame, regardless of which layout mode it's in.

Asymmetric pod-corner radius

80 16
80 16
Pod
shape
16 80
16 80
40 12
40 12
border-radius: 80px 16px 80px 16px; /* left-bean */ border-radius: 100px 100px 100px 100px / 50px 50px 50px 50px; /* center-bean (pod) */ border-radius: 16px 80px 16px 80px; /* right-bean */ border-radius: 40px 12px 40px 12px; /* gentle pod echo, default for blog cards */

The center-bean radius uses elliptical syntax (slash) for a pod shape. Use for primary/featured cards only. Side-bean radii for flanking elements. Gentle echo (40 12 40 12) as default for blog cards and generic tiles.

Dot markers — never bullets

li::before { content: ""; position: absolute; left: 0; top: 13px; width: 8px; height: 8px; border-radius: 50%; background: var(--primary); /* or --accent for premium */ }

Pod divider

The pod-and-three-beans compressed into a 120×24 horizontal divider. Use between major sections in Field Notes mode, between hero and masthead, and as an end-of-article rule. Centered with 48px margin above/below.

Three-bean service structure

When listing three services, products, pricing tiers, or practices, always map them to the logo's bean order:

PositionColorRoleExample
№ 01 · LeftSage greenFoundation / entryCustom Apps · Starter tier · Discovery phase
№ 02 · CenterGold — premiumCore value / most-chosenKinPlug Suite · Enterprise tier · Most-chosen plan
№ 03 · RightSage greenExtension / scaleAI Integration · Retainer tier · Ongoing support

The center position is always the premium/most-chosen. Never put a cheaper or less-flagship option in the center — it breaks the symbolism of the mark.

Floating pod decorations

Large pod SVGs at 6% opacity, rotated 15-30°, positioned near section edges (top-right, mid-left). Adds depth without competing with content. Pod & Bean mode only.

.pod-decor { position: absolute; pointer-events: none; opacity: 0.06; z-index: 0; } .pod-decor.top-right { top: 60px; right: -80px; width: 480px; transform: rotate(18deg); } .pod-decor.mid-left { top: 1200px; left: -120px; width: 360px; transform: rotate(-25deg); }
07 — UI Patterns

Interface elements.

Consistent components used across every page. Cream backgrounds, pill-shaped CTAs, generous whitespace, restrained color.

Buttons

Book demo See our work Read article →

Primary CTA uses Kintone red gradient. Ghost button uses sage green border. Inline link variant uses sage green arrow. All pill-shaped (border-radius: 100px). Min padding: 12px 24px.

Navigation

Sticky cream nav (rgba(250,250,248,0.95) with backdrop-filter: blur(12-14px)). Active link in sage green with optional gold dot indicator below. Same nav on every page. Book demo CTA always in the right slot.

Live data panel (Data Atelier mode)

EDAMAME · IN PRODUCTION● LIVE
Enterprise clients50active
Users across deployments2,443
Monthly recurring₱1.87M/mo

Ink background, gold border, 2px top-gradient rule (sage→gold→sage). Labels in JetBrains Mono uppercase. Values in DM Serif Display. "● LIVE" pulses. Wire to real endpoints where possible.

Cards

COMPARISON · 12 MIN
Kintone vs Odoo: the real picture.
Two platforms, two philosophies. We've deployed both.
Read article →
PRICING · 8 MIN
Odoo pricing PH: the total cost.
Real peso numbers after customization.
Read the note →

Left: standard card (Field Notes / Data Atelier mode) — 16px radius, 1px border, white/cream bg, 3px hover lift. Right: pod-echo card (Pod & Bean mode) — asymmetric 40px 12px 40px 12px radius, dot marker in top-left corner. Tags in JetBrains Mono uppercase. Titles in DM Serif Display.

Spacing & layout

TokenValueUse
Section padding (Y)clamp(48px, 8vw, 96px)All major sections
Container max-width1180pxContent rows
Container (narrow)840pxLong-form prose, FAQ
Card grid gap20-24pxStandard grid spacing
Border radius — cards16px (standard) / 40 12 40 12 (pod)Cards, sections
Border radius — buttons100pxAll CTAs, pills, tags
Button padding12-14px 22-28pxPrimary & ghost
08 — Homepage contract · NEW

Homepage contract.

The mandatory structural elements of the homepage. Every version going forward must include all of these. Added after v2.0 stripped key SEO & conversion elements and organic traffic declined.

  1. Sticky cream nav with pod logo, 4-5 links, and Book demo CTALinks required: Product / Customers / Notes (blog) / Pricing. CTA always in right slot.
  2. Hero with headline, lede, primary + ghost CTAHeadline uses DM Serif Display. At least one CTA to Calendly. Lede names pesos or a concrete number.
  3. Trust bar with 4-6 real client namesBelow the fold of hero. ORIX Metro, Daikin, Quipper at minimum. Visual or editorial presentation — never omit.
  4. Three practices section (the 3-bean structure)Apps · KinPlug (center, gold) · AI. Always in this order. Pod & Bean mode uses asymmetric radii; other modes use consistent 16px.
  5. Proof moment — live data panel OR named case studiesData Atelier: live panel + Gantt. Field Notes: named case dossiers (ORIX · Daikin · Quipper · AEON). Never omit both.
  6. Comparison section with linked competitor articlesMinimum 4 competitor comparison links (vs Odoo, vs Airtable, vs Salesforce, vs Monday). Editorial spec-sheet or comparison table. Each row anchors to a blog article.
  7. Field Notes / Knowledge Base — minimum 6 blog article linksSurface 6 specific blog articles with title + category + read time. NEVER fewer than 6 links. NEVER use shorthand path like /blog/ — always full /kintone-philippines/{lang}/blog/{slug}/.
  8. FAQ section with JSON-LD schema4-6 questions minimum. Use <details>/<summary> for accordion. Include FAQPage JSON-LD structured data for rich snippets.
  9. Pricing reference with 5-user minimum noted"Kintone starts at ₱1,000/user/month (5-user minimum)." Minimum subtly shown — 55% opacity or parenthetical. Engagement tiers (Starter/Enterprise/Retainer) referenced or linked.
  10. Final CTA with Calendly link"Thirty minutes with Tom. No pitch deck." Dark section, gold accent, single primary CTA. Never add contact form fields here — routes to Calendly only.

Violating any of these during a redesign requires explicit approval in the commit message. No exceptions — the v1→v2 regression cost measurable organic traffic.

09 — Content & blog · NEW

Content surfacing.

Rules for how blog articles, case studies, and editorial content surface across the site. Protects internal link graph and search discovery.

Path rules

ContextCorrect pathNever
EN blog index/kintone-philippines/en/blog//blog/ · /en/blog/
JA blog index/kintone-philippines/ja/blog//blog/ · /ja/blog/
EN article/kintone-philippines/en/blog/{slug}/Flattened paths
Calendlyhttps://calendly.com/kintoneph/freekintoneappconsultationShort/redirected URLs

Homepage blog surface

Minimum 6 article links from homepage. At least 3 in a "Field Notes" / "Knowledge Base" section with card treatment. Additional 3+ contextually embedded in comparison table, FAQ answers, or as inline links in service descriptions.

Card anatomy

ElementSpec
Category tagJetBrains Mono, 10-11px, uppercase, 0.18em tracking, sage green
Read timeMono, same spec, appended with " · 12 MIN" after category
TitleDM Serif Display, 20-24px, 1.2 line-height, never italic
DeckDM Sans, 14px, 1.55 line-height, muted color
Read CTA"Read article →" or "Read the note →" — sage green, 500 weight
Hover state3px upward lift + shadow + border color transition to sage

Structured data

FAQPage JSON-LD required on homepage. BlogPosting JSON-LD required on every article. Organization schema in root sitemap. Never skip structured data — it's why our FAQ snippets rank.

10 — Pricing reference

Priced by scope. Not by the hour.

Kintone itself starts at ₱1,000/user/month (5-user minimum — effectively ₱5,000/month floor). Our implementation services are priced per scope, no timesheets.

№ 01 · STARTER
₱95kone-time

Single app. 10-25 users. CRM, tracker, or simple workflow.

№ 02 · ENTERPRISE
₱450k+one-time

Multi-app workflow. 50-500 users. Full AI layer + KinPlug bundle.

№ 03 · RETAINER
From ₱85k/month

Ongoing build + optimization. Expanding deployments.

Copy conventions

ContextExact phrasing
Top of funnel (homepage, nav)"Starts at ₱1,000/user/month (5-user minimum)" — minimum subtle, 55% opacity
FAQ / buyer-ready"₱1,000 per user per month. 5-user minimum, so ₱5,000/month floor."
Sales conversation"Kintone pricing is ₱1,000 per user per month with a 5-user minimum — our implementation fee is on top."
Pricing page detailShow full table: users × ₱1,000 = monthly, with 5-user floor highlighted.
11 — Assets & files

Brand files.

All brand assets live in the root of the website repository.

FileUseFormat
edamame-logo-light.svgFull logo for light backgroundsSVG
edamame-logo-dark.svgFull logo for dark backgroundsSVG
edamame-icon.svgPod icon only (no wordmark)SVG
edamame-app-icon.svg512×512 green square for social/appsSVG
og-image-kintone-philippines.pngOpen Graph social sharing imagePNG 1200×630
brand-guidelines.htmlThis documentHTML
_backups/brand-guidelines-v1-2026-04.htmlv1.0 archive (April 2026)HTML

Repository

edamame-inc/edamame-website — Cloudflare Pages, auto-deploys on push to main. View this doc at /brand-guidelines.html.

1 design system, 3 layout modes, 82+ HTML pages. Same nav, footer, typography, palette, and homepage contract across every page.

Changelog

VersionDateSummary
v2.02026-04-22Three layout modes codified. JetBrains Mono added. Pod-motif patterns. Homepage contract. Blog surfacing rules. Pricing 5-user min.
v1.02026-04Initial brand system: logo, color, type, voice, UI patterns.