FAQ

Taqweed (تكويد) is a digital product team founded in 2021, working with brands across Saudi Arabia, the UAE, and the wider Gulf. One team covers the full product cycle: business framing, user research, brand identity, UX/UI design, engineering, motion and video, then post-launch partnership. We have delivered more than 27 digital projects and 17 brand identities.

An agency sells deliverables: a design or a website that ships, and the relationship ends there. A product team starts from the business question — who this is for, and what decision it should change — then stays past launch to measure and improve. At Taqweed, research, design, and engineering run as one track rather than as handoffs between separate vendors.

Nine specialists, each named on the team page: Bilal Reda, founder and UI/UX designer; Mostafa Mahmoud, senior full-stack engineer; Tarek Mohamed, software engineer; Mariam Khaled and Heba Abdelmoneim, UI/UX designers; Zeyad Gamal, Flutter developer; Omar Ahmed, WordPress developer; Islam Mohamed, brand identity and motion designer; and Youssef Sami, editor and 3D designer.

Directly with the people doing the work. Every project has named individuals rather than roles in a queue: you know who designs the interface, who writes the code, and who cuts the video, and you talk to them without a coordinator relaying messages between departments. The whole team is on GMT+3, an hour off Gulf time.

The team works from Cairo and serves clients in Saudi Arabia, the UAE, Kuwait, Qatar, Bahrain, and Oman. Projects run fully remote: scheduled Zoom reviews plus a direct channel on WhatsApp or Slack, on Gulf working hours. No part of the engagement requires being in the same room.

Yes. The Work page carries case studies explaining the problem, the design decision, and the result. The clearest is the eaalim platform redesign — UX and UI together, with a unified design system and component library — which produced a clearer signup journey and a measurable rise in enrolled students. For a sector-specific walkthrough, write to [email protected].

Yes — Redod, a SaaS platform we built and run ourselves. It pulls WhatsApp, Telegram, Messenger, Instagram, and others into a single inbox, with teams and per-user permissions, and AI agents that reply the way each business defines. It matters here as operational proof: we do not only design products, we build them and carry the cost of running them.

Both. The difference is scope, not attention. Startups usually come to build a first product version or an identity that holds up in front of investors; established companies come to redesign a platform already in use or to build an internal system. We scope after a requirements session, and we decline the project when we are not the right team for it.

A freelancer covers one discipline. Taqweed puts design, engineering, WordPress, mobile, motion, and video editing under one roof and one schedule. Work does not stall when one person is away, code is reviewed before it ships, and your files and repository stay in your name regardless of who works on them.

Six, each with its own page: brand identity and branding, UX/UI design, WordPress and WooCommerce development, custom web and application development, graphics and creative content, and post-launch support. Each is available on its own or combined into a single path from idea to launch. The scope of every line item is written and signed before work starts.

UX is the decision about how a product works: the user journey, the order of steps, and what gets removed to reduce friction — grounded in research and interviews, not taste. UI is the visible layer on top of that decision: grid, contrast, colour system, and reusable components. Products usually fail at UX before they fail at UI, which is why we design both together.

A full identity is a system, not a logo: competitor and positioning analysis, message and tone, a visual direction, the final logo in every format, colour and type systems, core applications, and a usage guide any team can apply after we leave. Eight deliverables, each named in the scope before we begin. We have delivered more than 17 identities so far.

WordPress is the right call for a company site, a blog, or a WooCommerce store you want to run yourself without a developer — and we build the theme from scratch rather than buying one. Custom development becomes necessary when the product carries its own business logic, complex integrations, or heavy load. We recommend the cheaper option whenever it meets the goal.

Yes — on WooCommerce with a custom theme, or inside a product built from scratch. The store ships connected to local payment gateways and shipping carriers with order status tracked inside the admin, plus management for products, variants, inventory, and coupons, and a measured before-and-after speed report. It does not go live until the full order and checkout path has been run with real orders on mobile and desktop.

Yes, as a service in its own right: dashboards, booking and order systems, client portals, and internal operations tools built around your process rather than a template. Delivery includes a requirements document, a database schema, full API documentation, roles and permissions, automated tests on the critical paths, and the complete repository in your name.

Yes. Zeyad Gamal on the team is a Flutter developer: one app running on Android and iOS from a single codebase, tested on real older devices rather than only on a simulator — because the phone in your customer's hand is not necessarily the newest one. We establish first whether an app is genuinely needed; plenty of cases are better served by a fast website.

Yes, and it is a discipline inside the team rather than something we subcontract: Islam Mohamed is a brand identity and motion designer, and Youssef Sami is an editor and 3D designer. That covers 2D and 3D animation, promotional video, and content editing. Output is built on your existing identity system, so the video does not look like it came from somewhere else.

Yes, and the clearest proof is Redod: our own platform, running AI agents that reply to customers across messaging channels the way each business defines. We also build automation flows that connect systems to each other and remove repetitive manual steps. Start with a session to establish what is actually worth automating — not every process saves time by being automated.

Yes, under graphics and creative content: campaign artwork, social assets at the correct platform sizes, presentations, and print material. Every piece is built on your existing identity system rather than improvised separately, and the work includes marketing copy in Modern Standard Arabic written for a Gulf audience.

Yes, and it is a large share of what we do. We start by reading what actually happens — where users stop, which screens get abandoned, and what already works and must not be touched — before drawing anything. The eaalim redesign is the published example: UX and UI together with a unified design system, producing a clearer signup journey and a rise in enrolled students.

Yes, and it is part of the build rather than an add-on: clean URL structure, titles and descriptions written per page, Schema.org structured data, a sitemap, and performance that passes Core Web Vitals. For AI-generated answers we write short, directly quotable passages and allow AI crawlers in robots.txt.

With a short brief through Smart Brief at brief.taqweed.com — about fifteen minutes, covering your goal, scope, and rough budget — or through the contact form. We reply within twenty-four hours with an initial proposal and a clear set of stages, and the first session is free with no obligation. No build starts before you sign a written proposal.

Seven: discovery, where we listen and work out who will use the product; definition, where we set a roadmap and agree what success is measured by; design; development into clean, scalable code; launch; growth, where we measure, learn, and improve; and ongoing support. A stage does not open until the previous one is approved in writing.

Less than most expect: a requirements session at the start, a weekly review of no more than thirty minutes, and a written approval at the end of each stage. What we need from you is the business decision and the authority to approve, not technical detail. The one delay we cannot absorb is late approvals or late content.

Yes. Every client gets a live task board showing each task, its status, its expected date, and who owns it, plus a weekly review and a written report at the end of each stage. You should never have to ask where the project stands.

The number of revision rounds is named in the scope before we start — never left open, never traded away later. At the visual direction stage we present more than one route with the reasoning behind each; if none convinces you, we redo the stage within the agreed rounds, before any build begins.

No. Your job is to explain the business: who the customer is, what decision you want them to make, and what counts as success. The technical side is entirely ours, and we explain every decision in business language rather than jargon — if you do not understand what we are working on, that is our failure, not yours. At handover you get hands-on training.

That is the normal starting point for most projects, and the discovery stage exists precisely for it. The first session is free: bring the idea, leave with a clearer plan, even if you go no further with us. We would rather start from an unpolished business problem than a pre-written feature list — a ready-made list usually hides the real question.

Yes — a formal contract covering scope, schedule, payments, intellectual property, and how either side can end the engagement. Payments are tied to delivery stages rather than to time, so if the project stops at a stage you receive the deliverables of what was completed and pay nothing for a stage that never started. Every clause is negotiable before signing.

There is no single price, and the spread is real: a few-page brochure site is a different project from a store wired to payments and shipping, and both differ from a platform with its own business logic. Send your scope and a written quote follows within twenty-four hours, itemised by stage and timeline. On a tight budget, start from the template library, where prices are fixed and published.

Five things: the number of unique screens or pages, how much research and content are required, the number and complexity of external integrations, whether the system needs roles and permissions, and how urgent the timeline is. Building on an existing foundation is always cheaper than building from scratch, and we say so plainly when it is enough for you.

Yes, and it is published on the services page: the more services in a single engagement, the larger the discount, reaching 30% on a bundle of five or more. The logic is operational rather than promotional — identity, interface, and engineering on one track removes the re-explaining and re-handover between vendors, and that saving goes back to you. Pick your services in the calculator on the page to see it.

A full brand identity starts at SAR 9,000 and takes three to five weeks. It covers brand discovery, more than one creative direction, the final logo in every format, colour and type systems, core applications, and a complete brand guide. The final figure depends on how many applications you need.

Brochure site or landing page: two to four weeks. Online store: four to eight weeks. Web app or custom system: eight to sixteen weeks depending on complexity. Full brand identity: three to five weeks. Library templates ship in three to ten days. The timeline is fixed in the proposal before signing, with a date against every stage.

Always. After the requirements session you receive a written proposal covering scope line by line, deliverables per stage, timeline, payments, the assumptions the price rests on, and explicitly what is out of scope. That last item is what prevents disputes later. No work begins before the proposal is signed.

Projects are split into three delivery-linked payments: 30% on signing, 40% at the midpoint, and 30% on final handover. We accept bank transfer and Visa/Mastercard in SAR, AED, or USD. Every payment is against named deliverables rather than against time spent.

Yes. Post-launch support packages start at SAR 1,500 per month and cover security updates, backups, uptime monitoring, bug fixes, and a set number of content-edit hours. The subscription is flexible with no long lock-in, and the tier can move up or down with your actual workload.

Yes, with no condition and no obligation. A thirty to sixty minute session covering your idea, your business goals, and a rough budget, and you leave with initial recommendations and a clearer roadmap even if you go no further with us. Book it from the contact page or on WhatsApp at +20 155 867 7588.

Ten ready-to-ship templates at fixed, published prices: six business sites, two landing pages, one online store, one dashboard — with N8n automation templates coming. They include Abqar, a SaaS product site with 69 pages per language at $399; Manara for a technology company at $199; and Sahwa, a landing page at $149. All built in Next.js.

Because marketplaces sell you a file and we sell you a working site — and the distance between the two is two weeks of grief and a developer invoice you did not budget for. Every template here is a neutral rebuild of a site we actually delivered and that carried real traffic, not an elegant design that never faced a deadline.

Installed, not zipped. No archive to unpack and no hunt for someone to set it up: we put it on your domain, wire up hosting, the SSL certificate, email, and the forms, and hand you a working link. The price is one-off and includes two revision rounds. Delivery takes three to ten days depending on the size of the template.

Genuinely Arabic — both Arabic and English are built on their own terms rather than one flipped from the other. Direction, typefaces, numerals, and dates are set correctly in each language; this is not an English template with a translation plugin bolted on that flips the direction and breaks the layout. You get both languages in the price, not one.

Yes, a full live preview: hit "Live preview" on any template and browse it page by page on desktop and mobile, with no signup and no card details. The demos are published on real domains such as apkar.taqweed.com and demo.taqweed.com, so what you see is what ships — not retouched screenshots.

You get thirty days of direct support from the same developer who installed your site — not a forum, and not a ticket waiting its turn. If you need more than that — extra pages, a system integration, custom development — you scale into a larger engagement without explaining your business again, because the team already knows your site.

Front end: Next.js, React, TypeScript. Back end: Node.js with PostgreSQL and Prisma. Mobile: Flutter or React Native depending on the project. Deployment and operations: Docker, Vercel, and Cloudflare, with Sentry for monitoring and Playwright for tests. For WordPress we build the theme from scratch instead of buying one. We pick the right tool for the project, not the one we are used to.

Yes — full, unconditional ownership once the final payment clears: source Figma files, the logo in every format, the complete codebase in a repository under your name, the database and a backup of it, and the domain and hosting registered to you. We keep no lock that forces you to stay with us.

Yes. Every site ships with a clear Arabic admin panel where you add pages, articles, and products, edit text and images, and manage orders without coming back to us. Fields are defined in advance so an edit cannot break the layout, and handover includes a recorded training session and a short guide.

Yes. We connect the site or system to payment gateways, shipping providers, CRM and ERP tools such as HubSpot, Zoho, and Odoo, and analytics and marketing platforms, over APIs or webhooks. We always ask for the other system's documentation and a test account before estimating — undocumented integrations are the single largest source of delay.

Yes, and we sign it before any sensitive detail is discussed rather than after the project starts. The contract that follows covers intellectual property, scope, schedule, payments, and how either side can end the engagement. We never publish a client's work in our portfolio without written permission.

Yes, and these are measured delivery conditions rather than general promises. Every interface is tested on mobile, tablet, and desktop, and we hand over a before-and-after speed report measured against Core Web Vitals. On security: SSL, regular updates, form spam protection, least-privilege accounts, and daily backups under the support packages.

Yes, and each language is built on its own terms rather than translated from the other: correct direction for each, Arabic typefaces chosen for reading rather than decoration, numerals, dates, and currencies formatted correctly per language, and copy that is written rather than machine-translated. That carries through to URL structure and language tags, so search engines index each version separately.

Launch sits in the middle of our process, not at the end — two further stages follow it: growth, where we measure, learn, and improve, and then ongoing support. We hand over files, access, and training, and stay close through the first two weeks, because the real problems surface with the first actual users. After that you continue on your own, or move onto a monthly support package.

Yes — sixty days from handover, during which we fix any code defect, compatibility issue, or performance fault at no extra cost. It does not cover new features, content your team adds, or outages in third-party services we do not run. Those limits are written into the contract rather than left implied.

Security updates for the system and its plugins, daily backups stored off the server, round-the-clock uptime monitoring, bug fixes, a set number of content-edit hours per month, and a monthly performance report compared against the previous month. Direct support by email and WhatsApp during working hours.

Yes — managed hosting on Vercel, AWS, Hetzner, or DigitalOcean depending on what the project needs, with initial setup, a CDN, and monitoring. Backups are daily and automatic for both database and files, stored on separate cloud storage with thirty days of retention. Accounts are registered in your name.

Yes. Final handover includes one or two Zoom training sessions of about an hour each, both recorded so they stay a reference for whoever joins your team later, plus a short Arabic guide to the most common tasks. The question channel stays open for two weeks after training at no extra cost.

Within twenty-four hours on new enquiries. New projects: [email protected]. General questions: [email protected]. Hiring: [email protected]. On WhatsApp: +20 155 867 7588, or by phone on +20 150 877 5889. Clients on a support package have a direct channel to the team during working hours.