What this covers
You can publish and update pages, products, and forms without a ticket, and you launch with a WordPress site that stays fast on mobile, tracks correctly, and keeps working after the next round of updates.
You’ll end up with a stable site you can edit in the block editor, with forms, tracking, and checkout tested before cutover. If you’d like to start, we’ll confirm scope and schedule the kickoff call.
We build on a clean theme setup with block patterns, then reduce risk as we go: audit plugins, remove what you do not need, migrate content with URL mapping, and test the parts that lose money when they fail (forms, analytics, payments). We do the work on staging, then cut over to live with a runbook and rollback plan.
A bit about us
We’re a three-person WordPress team that does builds and rebuilds, not a bit of everything. We started doing this work because most owners and marketing leads get stuck between design decisions and technical risk, and WordPress makes it easy to ship something that looks fine but breaks under updates, plugins, and real traffic.
We get picked when someone needs one team to take responsibility for the whole setup. We keep the theme and plugin stack understandable, we document the choices we make, and we test the parts that usually fail on launch day: forms, tracking events, redirects, and checkout flows. You get a site your team can run, and a clear path for changes after handover.
Meet the team
You’ll work with the same three people through build, testing, and launch, so questions get answered by the person doing the work.
Team
Laith Haddad, WordPress developer. Laith builds the theme, block patterns, and integrations, and keeps the build lean so updates do not turn into emergency work.
Dima Al-Masri, Project manager. Dima runs the timeline, keeps content and approvals moving, and makes sure redirects, tracking, and launch tasks do not slip.
Omar Khoury, QA and support lead. Omar tests across devices, checks forms and checkout end to end, and leads post-launch support and compatibility fixes.
Recent work
These are the kinds of WordPress rebuilds and WooCommerce setups we deliver when performance, editing, and launch risk all matter.
Portfolio
Service site rebuild. Rebuilt the theme with block patterns, reduced plugins, and cleaned up templates so the client could update pages in-house without breaking layouts. Migrated content and preserved URLs with a redirect map.
WooCommerce checkout fix. Reconfigured checkout, shipping, and payment settings, then traced failed orders back to plugin conflicts and theme overrides. Implemented fixes and added regression tests for checkout and transactional emails.
Performance tuning sprint. Improved Core Web Vitals by removing heavy front-end scripts, fixing image delivery, and tightening caching rules. Verified results in field data and re-tested key pages after plugin updates.
“Our site stopped breaking on mobile, and edits no longer feel risky.”
Marketing lead, inheriting an old WordPress site
WordPress theme setup
A custom theme or block theme setup that matches your design and keeps templates consistent across pages, posts, and key layouts.
BLOCK PATTERNS LIBRARY
Reusable page sections for your team to build and edit pages quickly in the block editor, with spacing and typography that stays consistent.
PLUGIN AUDIT REPORT
A written list of what stays, what goes, and why, including replacements where we remove a plugin that was doing too much or doing it poorly.
Content migration
+ URL MAP
Migrated pages, posts, media, and key content, plus a URL mapping sheet for redirects so old links keep working after launch.
WOOCOMMERCE CONFIGURATION
If your site sells, you get products, tax and shipping rules, payment methods, and checkout settings configured and tested with real-world scenarios.
LAUNCH CHECKLIST + HANDOVER NOTES
A launch checklist we run through on cutover day, plus handover notes so your team knows where key settings live and how to do common updates.
Pricing
Choose the tier that matches how much content and commerce you’re moving, and how much risk we need to manage during cutover. All prices are starting points.
Priced items
Get started
If you’re ready to lock in the slot, the signature and first invoice are what books the WordPress site build.
1. Sign this proposal to confirm the WordPress site build. 2. Pay the 30% booking invoice within 14 days. 3. Join the kickoff call and send access and content for staging.
Signature
Fee summary
Are you building on a custom theme or a page builder?
We build a custom theme or a block theme setup using the WordPress block editor, then add block patterns for repeatable layouts. We avoid page builders that add lock-in and slow the site unless you ask for one for a specific reason.
WHAT DO YOU NEED FROM US FOR CONTENT, AND WHO UPLOADS IT?
We’ll tell you exactly what we need in a content checklist: page copy, product details, images, downloads, and any legal text. We can upload and format content during migration, and we’ll show your team how to update it after handover.
How do we avoid losing Google rankings during the switch?
We keep URLs where we can, and where they must change we create a redirect map and test it before launch. We also carry over titles, meta descriptions, and structured content where it exists, then validate in Search Console after cutover.
WHAT HAPPENS WHEN WORDPRESS UPDATES BREAK PLUGINS LATER?
We reduce the chance of breakage by trimming plugins and avoiding risky overlaps, then we document what depends on what. If an update still causes a conflict later, we reproduce it on staging, fix compatibility, and retest the affected pages before it goes live.
Payment
We take 30% to book the work when you sign. The remaining 70% is due when the finished work is handed over. Each invoice is payable within 14 days of its date.
Change requests. If scope changes, we’ll list what changes and price it before we do the extra work. Small tweaks stay small. Bigger additions wait for your written approval so the handover date stays predictable.
What we need from you. We’ll send a content checklist for copy, images, downloads, product details, and legal text. You’ll send access and final content on the dates we agree, because migration and URL mapping depend on it.
Staging and go live. We build and test on a staging site, then cut over to live when you approve the launch checklist. We need DNS, hosting, and domain access in time to avoid a delayed launch window.
Content and redirects
Content migration and the URL map are based on what exists when migration starts. If large sections change after that point, we’ll update the redirect map as a change request and retest before launch.
Third party plugins and services. We can’t control changes in third party plugins, payment gateways, or shipping services. When something upstream changes, we reproduce the issue on staging, apply the safest fix we can, then retest affected pages.
Security and access. We’ll ask for admin access only where we need it, and we’ll keep it to named accounts. After handover, we recommend rotating passwords and removing any temporary access that was created for the build.
Ownership at handover. Once the final payment is made, you own the WordPress site build work we produced for you. You also keep control of your hosting, domains, and plugin licenses in your own accounts.
