Brand audit & marketing guidelines

The state of the brand, in one read.

Oviompt is a small product studio that ships software across web, mobile, desktop, cloud, SaaS, and AI. The brand presents as a quiet, opinionated, high-craft studio with a tight visual system, monochrome aesthetic, and a writing voice that rejects most conventions of the agency category (no team headshots, no logo wall, no testimonials carousel, no buzzwords).

The audit finds the brand is unusually coherent for a studio of this size. The website, design system (Spine), case studies, and writing all express the same idea: finite engagements, measurable outcomes, no theater. That coherence is the strongest commercial asset Oviompt has, and the largest risks to the brand are dilution risks (taking on work that doesn't fit the voice, broadening services without sharpening the message, or hiring contributors who write differently).

The audit recommends six things, in order of priority:

1. Hold the voice. The voice is the moat. Any new contributor writes against the voice rules in Part 2.
2. Tighten the audience message. The site now serves both first-time founders and CTO-grade buyers. Both work, but the home page should explicitly name both groups.
3. Publish a contributor brief. Anyone writing under the Oviompt byline reads the voice rules and the do-not list before publishing.
4. Lock the visual system. Spine v0.1 is solid. Document the tokens and the rules so the next surface (proposals, decks, invoices) inherits them.
5. Build a proof flywheel. Every shipped engagement produces one case study, one short writeup, and one social post within 14 days of launch.
6. Measure two numbers, weekly. Inbound intent submissions per week, and the conversion from intent to scoped engagement.

What's true today.

Where Oviompt sits.

What Oviompt is

A small software studio that takes finite-scope product engagements and ships them in a defined window. The studio commits to a date, a price, and a measurable outcome before work starts. The studio writes about how it makes decisions, not about how big it is.

What Oviompt is not

Not an agency. Not a body shop. Not a generalist consultancy. Not a no-code shop. Not a venture studio. Not an "AI agency." The brand has decided what to refuse, which is half of positioning.

Position on three axes

Craft vs. throughput. Oviompt sits on the craft end. The studio ships fewer things, more carefully. Throughput shops compete on volume; Oviompt competes on the quality of the artifact and the clarity of the decisions behind it.

Generalist vs. specialist. Oviompt is a deliberate generalist across surfaces (six surfaces named explicitly), but a specialist in how it works: finite windows, measurable outcomes, a written decision register per project. The "method" is the specialism.

Anonymous vs. founder-led. Oviompt has chosen anonymous-studio positioning. No founder face. No team page. This is unusual and high-conviction. It signals that the work, not the personalities, is the product.

Positioning sentence (current, implicit)

"Oviompt is a small studio that ships software products across web, mobile, desktop, cloud, SaaS, and AI in finite windows with measurable outcomes."

This sentence is correct. It is also too long. See Part 2 for the recommended canonical positioning sentence.

What the brand looks like, today.

Logo

The mark is two overlapping circles, a Venn-style figure read as the "intent → impact" loop. The mark is monoline, scales cleanly to a 16px favicon, and works in light and dark themes via currentColor. The mark is held in stroke (1.6 weight), never filled. This is a strong, durable mark.

Findings. The mark works at all required sizes. No re-design needed. Document the construction in Part 2 so it can be reproduced consistently in decks and print.

Typography

Two typefaces, both open source, both available on Google Fonts.

• Hanken Grotesk — primary sans. Used for body and headline. Weight range 300–800. The italic carries the small "emphasis" gestures across the site.
• JetBrains Mono — monospace. Used for IDs, labels, metadata, code, the engagement-ID numbering (OV-###), and the section markers (§ 01, D · 01).

Findings. The pairing is distinctive without being precious. Hanken Grotesk is uncommon enough to read as "considered" without being so unusual that licensing or fallback becomes a problem. JetBrains Mono carries the "we are technical" signal without leaning on Geist or IBM Plex (both of which are now category clichés).

Color

Strict monochrome with no accent. Theme tokens are CSS custom properties (--ink, --bg, --rule, --ink-2, --ink-3). Dark mode is the default; light mode is fully wired with WCAG 2.2 AA contrast across all text tiers.

Findings. Monochrome is the right call for the category. Every other AI/dev studio in 2026 is reaching for gradients, glow, or pastel. Holding monochrome makes Oviompt look older, more confident, and less algorithmically generated.

Layout language

The site uses a "decision register" layout pattern: numbered sections (§ 01, § 02), labeled rows (D · 01, D · 02), and meta dl blocks (ID / Year / Client / Duration / Team / Surfaces / Status). The pattern reads as engineering documentation rather than marketing copy.

Findings. This is the single most distinctive visual choice. It signals method without claiming method. Hold it across all future surfaces.

Motion and imagery

Reduced motion. The intent meter pulses; the ship feed ticker rotates. Nothing else moves. Honor prefers-reduced-motion.

Effectively no photography. No stock. No AI-generated illustrations. The site uses typography, rules, numbers, and the brand mark as its visual content. Hold this.

How the brand sounds.

Voice attributes (observed)

1. Quiet. No exclamation points. No "we're excited to announce." No emoji. Confidence comes from specificity, not volume.
2. Specific. Numbers are exact and small ("Booking · 1 slot," "14 weeks," "−47%"). Vague claims are absent.
3. Opinionated. The site says what it doesn't do as often as what it does.
4. Plain. Short sentences. Common words. No jargon.
5. Self-aware. The brand acknowledges constraints (one slot, finite windows) and turns them into selling points.
6. Welcoming to first-time founders. Recently added explicit language widens the door without changing the voice.

AI-tells the voice avoids

The voice has been deliberately sanitized of phrases that read as LLM-generated marketing copy: no em-dashes between clauses, no "it's not just X, it's Y" constructions, no "delve / tapestry / navigate the landscape," no three-item triples, no "moreover / furthermore / in conclusion."

Who's reading.

The brand serves four distinct audiences with one voice. This works because the voice is "plain, specific, opinionated," which reads as respectful to all four. The risk is that home-page messaging can favor one audience and accidentally exclude another.

Current audiences:

1. First-time founders (technical or domain expert). Buy First Ship MVP or an Audit.
2. CTO / VP Engineering at growth-stage companies. Buy Multi-surface build or a Service engagement.
3. Product leaders at SMBs. Buy a Service engagement (e-commerce, ERP/Dynamics, integrations, workspace).
4. Domain experts turning operator (lawyers, clinicians, ex-operators). Buy Audit, then First Ship MVP.

Findings. The current home page handles this by naming engagement tiers explicitly and adding "First-time founders are welcome here." This is sufficient. Do not segment the home page by persona; segment the proof (case studies, blog posts) by audience.

Where the studio competes.

The studio category is crowded. Oviompt's competition falls in three groups: boutique product studios, AI-first agencies (the 2024–2026 wave), and freelancer collectives. Oviompt competes against each by refusing the playbook each runs.

Differentiators that hold up under scrutiny

• Six surfaces, not one. (Most studios are web-only or mobile-only.)
• Finite windows with stated outcomes. (Most studios sell time-and-materials.)
• A written decision register per project. (Almost no studio publishes this.)
• Anonymous studio positioning. (Counter-cultural in a founder-LinkedIn world.)
• Pricing on the page, in USD, on the studio surface. (Most agencies hide pricing.)

Vulnerabilities

• No named founder means trust takes longer to build with first-time buyers. Mitigation: detailed case studies, plain pricing, audit-tier as a low-commitment first step.
• Anonymous positioning makes social proof harder. Mitigation: build a proof flywheel.
• Six surfaces is a lot to be credible across. Mitigation: lead with the surface that matches the buyer's intent.

What works, what's missing, what could break.

Strengths

1. Distinctive voice that is hard to copy.
2. Coherent visual system (Spine v0.1) across every page.
3. Pricing on the page, in USD, with realistic ranges.
4. Six shipped case studies with telemetry, not testimonials.
5. SEO/AEO infrastructure already in place (sitemap, robots, schema, canonical, OG, redirectors).
6. WCAG 2.2 AA accessibility achieved.
7. Lighthouse 100 across performance, SEO, best practices, accessibility.
8. Two-tier intent form lowers the friction of first contact.

Gaps

1. No proposal template using the Spine system.
2. No deck template using the Spine system.
3. No invoice / SOW template using the Spine system.
4. No contributor brief for new writers / contractors.
5. No newsletter capture on the writing pages.
6. No measurement system for inbound (intent → scoped engagement).
7. Limited proof on the e-commerce and ERP/Dynamics service lines.
8. No "from the studio" cadence beyond episodic case studies.

Risks

1. Voice drift. New contributors write in their own voice; the brand erodes.
2. Service sprawl. Eight services is the ceiling; adding a ninth dilutes the message.
3. Anonymity vs. trust. First-time founders may want to see a face. Mitigate with the audit tier.
4. AI-tell creep. As content scales, AI-tell phrases will reappear unless rules are enforced.
5. Pricing confusion. USD-primary on a global studio surface needs an INR-on-request line.

Priority order.

What we promise. What we are.

Brand promise

Intent → impact. We turn a clear intent into a shipped product, in a window we agree on, against an outcome we measure.

Canonical positioning statement

Oviompt is a small product studio. We ship software across web, mobile, desktop, cloud, SaaS, and AI, in finite windows with measurable outcomes. First-time founders are welcome.

Short forms

• One line: "A small studio that ships software in finite windows."
• Six words: "Intent to impact, finite and measurable."
• Three words: "Intent → impact."

Why the studio exists.

Mission

To make it possible for a small number of clients each year to turn a clear intent into a shipped product, without the theater that usually surrounds software work.

Vision

A studio that is known for the quality of its decisions, not the size of its team. A studio whose case studies could function as engineering documents on their own.

Values

1. Specificity over scale. A small number of well-shipped things beats a large number of vague things.
2. Decisions, written down. Every project produces a decision register. The register is the artifact, not the slides.
3. Finite windows. A start date, an end date, and a measured outcome. No open-ended retainers.
4. Refuse what doesn't fit. Saying no is a brand asset. We say no often.
5. Plain language. If a sentence requires the reader to look up a word, rewrite the sentence.
6. First-time founders are welcome. We do not patronize, and we do not over-charge for first products.

Who we serve.

Persona 1 — The First-Time Founder

A domain expert (clinician, lawyer, teacher, operator) or a technical person who has never run a software project. Buys First Ship MVP ($12k–$45k) or an Audit ($3k–$10k). Fears being upsold, condescended to, trapped in a long contract. Voice register: direct, slightly warmer, no jargon.

Persona 2 — The Buyer-Side CTO / VP Engineering

Engineering leader at a Series B–D company. Buys Multi-surface build ($120k–$500k) or a Service engagement. Fears hand-off problems, vendor lock-in, theater. Voice register: forensic, technical, no marketing.

Persona 3 — The SMB Product Owner

Owner-operator or VP at a 20–500 person business. Buys a Service engagement ($2k–$35k). Fears disruption to the business, surprise costs, long onboarding. Voice register: direct, business-outcome-focused.

Persona 4 — The Domain Expert Going Operator

A senior practitioner building their first product around their expertise. Buys Audit, then First Ship MVP, often a Multi-surface build over 18 months. Fears their expertise being flattened into generic software. Voice register: respectful of expertise, plain about software realities.

The brand, drawn.

Logo construction

Two overlapping circles, monoline, stroke weight 1.6 in a 24×24 viewBox.

Left circle:  cx=9,  cy=12, r=8
Right circle: cx=15, cy=12, r=5.2
Stroke:       currentColor, 1.6
Fill:         none

The mark uses currentColor so it inherits the text color and works in any theme.

Logo rules

• Always monoline. Never filled.
• Always uses currentColor. Never hard-coded to black or white.
• Minimum size 16px (favicon). Below this, do not use.
• Clear-space margin equal to the height of the smaller circle.
• Pairing with wordmark: "Oviompt" in Hanken Grotesk 600, baseline-aligned with mark center.
• Never rotate, recolor, apply effects, or recompose with other marks.

Typography system

Color tokens (production values)

--ink:   #FFFFFF;   /* default text on dark */
--ink-2: #B5B5B5;   /* secondary text, WCAG AA */
--ink-3: #9E9E9E;   /* tertiary text, WCAG AA */
--rule:  #2A2A2A;   /* hairlines on dark */
--bg:    #000000;   /* default background */

For the light theme, invert: --ink: #000, --bg: #FFF, --ink-2: #444, --ink-3: #6B6B6B, --rule: #E2E2E2.

Color rules. No third color. No gradient. No shadow. The brand is monochrome.

Layout language

The "decision register" pattern is the brand's defining layout. Use it across all surfaces: numbered sections (§ 01), labeled rows (D · 01), meta dl blocks (ID / Year / Client / Duration / Team / Surfaces / Status), telemetry cards (large number, label, caption), stack rows (Layer / What / Why).

Motion and imagery

Hover/focus transitions: 180ms ease. Theme switch: 200ms. Honor prefers-reduced-motion. No parallax, no scroll-jacking, no autoplay.

No stock photography, ever. No AI-generated illustrations under the Oviompt mark. Schematic SVG diagrams are allowed when they clarify a decision. Screenshots of shipped surfaces are allowed in case studies, with the client's permission.

How we write.

The voice in one sentence. Plain, specific, opinionated, quiet.

Always

• Use short sentences. Cut the second clause if it starts with "and" or "but."
• Use exact numbers ($12k, 14 weeks, −47%, 7 models).
• Name what you don't do as often as what you do.
• Lead with the decision, not the description.
• Write the way a senior engineer talks at a kitchen table.
• Use the active voice.
• Use first-person plural ("we"), not third-person.

Never

• Never use em-dashes between clauses. Use a period or comma.
• Never use "it's not just X, it's Y" constructions.
• Never use "delve," "tapestry," "navigate the landscape," "in today's fast-paced world," "robust," "best-in-class," "cutting-edge," "leverage," "synergy," "transformative."
• Never use three-item triples ("fast, scalable, and reliable"). Pick the most important one.
• Never use "moreover," "furthermore," "in conclusion."
• Never use exclamation points outside of error messages.
• Never use emoji in marketing copy.
• Never use stock metaphors ("at the end of the day," "moving the needle," "low-hanging fruit").

Voice register by surface

What we say.

Headline messages (in order)

1. Intent → impact.
2. A small studio that ships software across web, mobile, desktop, cloud, SaaS, and AI.
3. Finite windows. Measurable outcomes. First-time founders welcome.

Proof messages

• Six surfaces shipped, with telemetry on every case.
• Pricing on the page, in USD, with realistic ranges.
• A written decision register on every project.
• One slot at a time. Currently booking Q3 2026.

Anti-messages

Not an agency. Not a body shop. Not a no-code shop. Not an AI agency. Not a venture studio. Not a generalist consultancy.

Service-line messaging (one sentence each)

Detail rules.

Headings

Sentence case. Never title case. One H1 per page. Subsequent levels in order.

Numbers

Use digits for all quantities ("1 slot," not "one slot"). Currency with k for thousands. Percentages always written as digits with %. Dates as "2026" or "2026 · Q3."

Punctuation

• Use the Oxford comma in lists of three or more.
• Use the en-dash (–) for ranges only.
• Do not use em-dashes (—) between clauses. Use a period or comma.
• Use the pipe (|) as a separator in titles.
• Use the middle dot (·) as a separator in metadata.

Lists, links, acronyms

Use bullets only when order does not matter. Link text must be meaningful out of context (never "click here"). Spell out acronyms on first use. Pluralize without apostrophes ("APIs," not "API's").

What we measure.

North-star goals (annual)

1. Maintain one slot available at all times.
2. Book the year on inbound only (no outbound sales).
3. Convert 25% of detailed intent submissions into scoped engagements.
4. Publish 24 long-form posts per year.
5. Ship 6–8 case studies per year (one per closed engagement).

Operating KPIs (weekly)

How they arrive.

Visitor → Reads ≥ 1 case study → Submits intent (low-friction or detailed)
       → Studio responds within 48h → Discovery call
       → Scoped engagement (proposal accepted)
       → Shipped → Case study → Loop

Top of funnel. Long-form blog posts, case studies, and the studio page ranking for high-intent technical queries. AEO answers in Perplexity, ChatGPT, Claude.

Middle of funnel. Method page, studio page, second or third case study read in the same session.

Bottom of funnel. Intent form (low-friction or detailed), direct email to [email protected].

Post-intent. Studio response within 48h, written. Discovery call (30 min). Written proposal in decision-register format within 5 working days.

Where we show up.

Owned (priority 1)

The site is the primary channel. Every other channel exists to push to the site. Blog: long-form essays, two per month. Case studies: one per closed engagement, within 14 days of launch.

Earned (priority 2)

Organic search via SEO (already in place). Inclusion in Perplexity, ChatGPT, Claude, Gemini answers via AEO infrastructure (already in place; track manually monthly). Inbound mentions when a case study is shared.

Operated, narrowly (priority 3)

One newsletter, monthly digest only. One social channel (LinkedIn or X), one post per week, mirroring the site's writing.

Refused

Paid ads. Cold outbound. Sponsored content. Webinars. Event sponsorships. Podcast hosting.

30 / 60 / 90.

Days 1–30

• Publish the contributor brief (one page, derived from § 14).
• Audit existing blog posts against voice rules; rewrite any AI-tells.
• Add newsletter capture to /blog/ index and home CTA.
• Set up the weekly KPI dashboard.
• Publish 2 long-form posts and 1 short "from the studio" note.

Days 31–60

• Build proposal and deck templates in Spine.
• Publish 2 long-form posts, 1 short note, 1 case study.

Days 61–90

• Build SOW and invoice templates.
• Quarterly brand review against this document.
• Publish 2 long-form posts, 1 short note, 1 case study (if available).
• Send first monthly newsletter.

Editorial themes (annual)

1. Shipping software in finite windows.
2. The case for written decision registers.
3. Why AI-tell phrases hurt your brand.
4. Pricing software work in plain English.
5. The first thing to ship (for first-time founders).
6. The trade-offs in choosing a stack.
7. Observability before optimization.
8. Why we refuse retainers.

From interest to engagement.

Capture

Two-tab intent form on /intent/. Tab 1 (Just say hi): 3 fields, no barrier. Tab 2 (File detailed intent): 7 fields, detailed brief.

Routing

All submissions land in [email protected]. A single member is on rotation to triage within 48h.

Qualification (asked on the discovery call)

1. What is the intent in one sentence?
2. What surface? (Web, mobile, desktop, cloud, SaaS, AI.)
3. What is the measurable outcome that would make this a success?
4. What is the window?
5. What is the budget range? (USD.)
6. Who decides?
7. What have you ruled out, and why?

Disqualification

Open-ended retainer with no defined outcome → decline politely, refer out. Budget below the floor for the requested surface → propose an Audit instead. Window too short → propose a smaller scope. Committee buyer with no decision-maker → propose an Audit to surface them.

How we talk about price.

Display rules

• USD is the primary display currency.
• Ranges, not single numbers ("$12k–$45k").
• INR available on request, not displayed per-card.
• Pricing is on the studio page, never hidden behind a form.
• Per-engagement, never per-hour. Oviompt does not sell time.

Range guidance

Conversation rules

• Quote in writing, never on a call.
• Quote a fixed fee where possible. If not, quote a not-to-exceed range with a written contingency clause.
• Never discount for speed. Discount only for scope reduction.
• Never quote without a defined outcome.

Assets we carry into every conversation.

1. The site. Pre-read by the buyer 80% of the time.
2. A case study deck. 6 case studies in the Spine system.
3. The proposal template. Decision-register format, in Spine, sent within 5 working days.
4. The SOW template. Plain English, fixed-fee where possible.
5. The hand-off doc. Delivered on day one of every engagement.

The discovery call

30 minutes. Video. No deck. Studio asks the seven qualification questions and shares its read in plain language at the end.

The proposal

Always opens with a one-sentence restatement of the intent. Always includes scope, out-of-scope, window, price, assumptions, and a single decision the buyer needs to make to accept. Never includes marketing copy, logo wall, testimonials, or "about us."

The hand-off

Day one of every engagement, the buyer receives a one-page written hand-off doc covering: who is on the engagement (roles, not names), what the cadence is, where the artifacts live (buyer's choice of tool), when the milestones are, how decisions get logged.

How often we look.

Weekly (Monday, 30 min)

Intent submissions in. Detailed-intent → scoped conversion rate (rolling 8 wks). Posts shipped. Engagements active and percent through window. One blocker, written down.

Monthly (first Monday, 60 min)

Search console: top 20 queries, top 20 pages. AEO sample: 6 questions in Perplexity, ChatGPT, Claude. Newsletter performance. One thing to change, written down.

Quarterly (first Monday, 2 hrs)

Read this document end-to-end. Update the brand snapshot. Audit voice across the quarter's writing. Audit visual system across new surfaces. Decide if one rule needs to change.

Annual (year-end, half day)

Update audience personas based on the year's actual buyers. Refresh case study list and pricing ranges. Refresh the canonical positioning sentence. Decide what to refuse next year.

Pricing reference (canonical).

INR pricing available on request (do not display per-card).

Stack and services snapshot.

Surfaces

Web, mobile, desktop, cloud, SaaS, AI.

Stack categories (open-source first, no lock-in)

Services (eight)

S01 Custom development · S02 SEO and AEO · S03 E-commerce · S04 ERP and Microsoft Dynamics · S05 Integrations and automation · S06 Workspace setup · S07 Cloud and DevOps · S08 Audits.

Brand voice examples.

Hero copy

Service description

Pricing line

Email reply (intent submission)

Asset checklist.

Currently in place

• Site (oviompt.com) with all required pages
• Design system (Spine v0.1) in CSS custom properties
• Logo (SVG, monoline, currentColor)
• Typography stack (Hanken Grotesk, JetBrains Mono via Google Fonts)
• OG image (1200×630 SVG)
• Favicon (inline SVG)
• Sitemap, robots.txt, redirectors
• Schema (Organization, WebSite, ProfessionalService, FAQPage, HowTo, Article, CreativeWork, BreadcrumbList)
• Two-tab intent form
• WCAG 2.2 AA across the site
• Lighthouse 100 across the four categories

To build (next 90 days)

• Contributor brief (one page, derived from § 14)
• Proposal template in Spine
• Deck template in Spine
• SOW template in Spine
• Invoice template in Spine
• Hand-off doc template
• Newsletter capture on /blog/ and home CTA
• Weekly KPI dashboard
• Monthly AEO sampling log
• One e-commerce or ERP case study

To refuse (forever)

• Stock photography
• AI-generated illustration under the Oviompt mark
• Founder headshots / team page
• Logo wall on the site
• Testimonial carousel
• "Featured in" badges
• Hourly billing
• Open-ended retainer
• Cold outbound
• Paid ads