The build
What we build.
We build a WordPress block theme with your design tokens in theme.json, a library of components, and patterns your team assembles into pages. Native WordPress throughout, with no page-builder layer to carry and nothing between your editors and the CMS.
The measure of success is simple: your marketer can ship a new landing page on a Friday afternoon, on their own, and be confident it will look right.
Approach
How it works.
Components, then pages. We build the parts (hero, feature grid, quote, comparison table, call to action) and pages are assembled from them. That is what makes the second year as fast as the first.
Freedom where it helps, guardrails where they help more. Marketing can change text, images, order and colour within the palette. The layout stays intact whatever happens. That boundary is what makes the freedom safe to use.
Handed over properly. A short training session or recorded videos, plus a page inside the admin that documents every pattern. Then it is yours.
Your team
What you can change without us.
- Any text and any image, including navigation and footer
- Add, remove and reorder blocks on any page
- Build a new page from existing components
- Duplicate a landing page, change the headline, publish on a new URL
- Section backgrounds, within the brand palette
Where we stay involved
- New component types, or changing how one behaves
- Integrations: CRM, marketing automation, product data
- Content model, URL structure and redirects
A short list on purpose, and the part where having us on hand pays for itself.
AI for your team
Connected to Claude, if you want it.
Your team can work with the site by asking for what they need. “Draft a post about the new GraphQL scanning feature, in our house style.” “Update the pricing page: enterprise now includes SSO.” The draft appears in WordPress, ready for someone to review.
It is the same promise as the rest of this page, one step further: your marketing team publishes without waiting on a developer, and now without opening every screen by hand.
A person always decides. Claude drafts, prepares and suggests; your editor approves and publishes. That boundary keeps your voice consistent and your quality where you set it, and it is how we configure it by default.
What it is good for
- Drafting posts and pages from a brief, in your established voice
- Alt text, meta descriptions and schema across a whole library in one pass
- Finding content that has gone stale and suggesting what to refresh
- Internal linking suggestions across the site
- First-pass Hebrew translations for a human to review
How we set it up
We use the official wordpress/mcp-adapter, the implementation the WordPress core team actively develops, with the deepest integration into the Abilities API. That lets us grant exactly the capabilities you choose and nothing else.
- Scoped permissions, decided with you, rather than blanket admin access
- Set up and tested on staging before it touches production
- An audit trail of what changed, and a clean way to roll back
- Written down, so the next person on your team can pick it up
It works with Claude and with any other assistant that speaks MCP. The connection is to a standard, not to one vendor.
Hebrew & English
Multi-language and right-to-left.
We build bilingual sites including Hebrew with full right-to-left layouts. Direction affects motion, iconography, form flow and typography, so we design and build for it from the start. The Minrav Group site is bilingual with RTL throughout.
Speed
Performance is a build decision.
Core Web Vitals are decided while building. The budgets we hold ourselves to: LCP under two seconds, CLS effectively zero, and interactions responding within 200ms. Images ship in modern formats, and each page loads what it needs and nothing else.
FAQ
Questions we get asked
How long does a B2B WordPress site take?
Six to ten weeks from kickoff to launch. Strategy and content structure take the first one to two weeks, design two to three, build two to three, QA and accessibility the last week. Projects move fastest when content and approvals come back quickly, so we plan around that.
Why native blocks rather than a page builder?
Native blocks keep the site light and keep you portable: any WordPress developer can pick it up. It is the choice that ages best.
Can we host it ourselves?
Yes. You own the code, the server and the access from day one. We are happy to recommend hosts, and equally happy to work with yours.
Can Claude publish to our site on its own?
The setup we build has a person approve anything before it goes live. Claude drafts and prepares; your editor decides. That keeps your voice and your standards intact, and it is what makes the workflow trustworthy enough to use.
Is it safe to connect an AI assistant to our website?
Yes, when the permissions are scoped. We use the official WordPress MCP adapter with the Abilities API, so the assistant gets exactly the capabilities you choose. We configure it on staging first, keep an audit trail, and make sure there is a clean rollback.
Does it have to be Claude?
No. The connection uses MCP, an open standard, so it works with Claude and with other assistants that support it. You are connected to a protocol, not locked to a vendor.
How does pricing work?
Fixed scope, quoted in full before work starts, so you know the number in advance. Changes after launch are pay-as-you-go. We walk you through it on the first call.
Next step
See it running.
Look at sites we have built, or tell us about yours.