// Service · UI/UX Design
UI/UX
& Design
Good design is invisible. You just do what you came to do.
Most people think design is about how something looks. It isn't. It's about how it works. A beautiful website where users don't know where to click — that's a failed website. A stunning app that takes five minutes to place an order — that's money walking out the door.
// 01 · The method
Good design starts with one question:
Why is the user here?
And we work backwards — what does the user need to do, how do we make it as easy as possible, and how do we make it feel completely natural. We have a full in-house UI/UX department. Not an external freelancer drawing pretty screens — a team that works hand-in-hand with the developers, knows what's possible and what isn't, and doesn't sketch dreams that can't be built.
// Where you start
What has to be planned before development?
Three things decide what to specify and design: the business need, who the users are, and the state the product is in today. The deliverable follows from that — not the other way round.
- 01
An idea, no document
The first question is who the user is and the one action they must complete. The right deliverable is a short requirements document and a screen map — not final design.
- 02
Requirements exist, interface needed
The requirements are written, but no one has seen a screen yet. This starts with wireframes and a clickable prototype, and only then UI design.
- 03
A live product, something isn't working
Before a redesign — understand where users get stuck. A short study of the current product decides whether to change a flow, a few screens, or everything.
// 02 · What we do
What we do
Research, UX strategy, UI design, prototypes, design systems, and dedicated mobile design — end-to-end.
- 01
UX strategy
Before we draw anything, we understand. Who's the user, what do they want, where do they get stuck. Without this, you're designing in a vacuum.
- 02
UI design
The final screen. Colors, typography, icons, interactions. Beautiful, sure — but more importantly, functional.
- 03
User research
Interviews, surveys, usability testing. Because opinions aren't data.
- 04
Wireframes & prototypes
Before investing in development, you see how it feels. Test, change, iterate.
- 05
Design systems
For large products — a full design system. Components, colors, rules. Consistency in the product, speed in development.
- 06
Dedicated mobile design
An app isn't a small website. Mobile-first design that respects the platform.
- 07
Digital brand design
Logo, color palette, typography, visual style. Your identity, in digital form.
// Which deliverable fits
Requirements document, specification, prototype and design — not the same thing
Four different deliverables answering different questions. You can commission one, some, or all of them in sequence — but not substitute one for another.
| Deliverable | What it answers | What it contains | What it is not |
|---|---|---|---|
| Requirements document | What the product must enable, for whom, and what is out of the first version | Users and roles, main scenarios, requirements and constraints, acceptance criteria | Not screens and not a technical solution |
| UX specification | How the user moves from step to step | Screen map, flows, information architecture, black-and-white wireframes, error and empty states | Not final design and not code |
| Interactive prototype | Whether the flow makes sense before any code is written | Linked clickable screens, states, notes for testing with users | Not a working product — no real data, no backend |
| UI design and handoff | How each screen actually looks and behaves | Final screens, components and design system, spacing and typography specs, developer assets | Not a substitute for specification — a beautiful screen on a wrong flow is still wrong |
Requirements document
What it answers: What the product must enable, for whom, and what is out of the first version
What it contains: Users and roles, main scenarios, requirements and constraints, acceptance criteria
What it is not: Not screens and not a technical solution
UX specification
What it answers: How the user moves from step to step
What it contains: Screen map, flows, information architecture, black-and-white wireframes, error and empty states
What it is not: Not final design and not code
Interactive prototype
What it answers: Whether the flow makes sense before any code is written
What it contains: Linked clickable screens, states, notes for testing with users
What it is not: Not a working product — no real data, no backend
UI design and handoff
What it answers: How each screen actually looks and behaves
What it contains: Final screens, components and design system, spacing and typography specs, developer assets
What it is not: Not a substitute for specification — a beautiful screen on a wrong flow is still wrong
// 03 · Our approach
Our approach
- 01
Design is a business decision, not personal taste
Every design decision has to answer one question — does it move the user toward the right action? If not, it's noise.
- 02
Designers in constant conversation with engineering
A designer who doesn't understand how the code works is sketching dreams. We don't.
- 03
Less is more
Cluttered design is bad design. We strip away until only what's necessary remains.
- 04
Accessibility from day one
Inaccessible design isn't good design — it's design that leaves people out. We design to EAA and WCAG standards from day one.
// 04 · Our toolkit
We don't fall in love with tools — we pick the right one for the job.
From Figma to Framer, from Hotjar to Storybook, from Maze to axe DevTools. Tools change, the method stays — understand, measure, improve.
- Design
- Figma
- Adobe XD
- Photoshop
- Illustrator
- Prototyping
- Figma
- Framer
- ProtoPie
- User research
- Maze
- Userbrain
- Lookback
- Analytics
- Hotjar
- Microsoft Clarity
- FullStory
- Design systems
- Storybook
- ZeroHeight
- Tokens Studio
- Accessibility
- axe DevTools
- WAVE
- Stark
// 05 · How we work
How we work
- 01STEP 1
Understand the product & user
Who are they? What do they want? What annoys them in competing products? Every answer is a design input.
- 02STEP 2
UX architecture
User flows, sitemaps, information architecture. The skeleton before the skin.
- 03STEP 3
Wireframes
Black-and-white screens. No colors, no images, just structure. If it doesn't work here, no amount of color will save it.
- 04STEP 4
Hi-fidelity design
Final screens. Colors, icons, typography, micro-interactions.
- 05STEP 5
Interactive prototype
Screens connect to screens, animations, states. You see the product alive before a single line of code.
- 06STEP 6
Developer handoff
Not "hey, draw it like this." A full handoff with design system, specs, assets. Developers can start immediately.
- 07STEP 7
Support during development
The designer stays available. Because there are always questions, and always small decisions that need to be made.
// What we need from you
How we work together — and how scope gets approved
Good specification and design depend on information only you hold. This is what we will ask for, and these are the decision points where you approve before we move on.
- 1
Information from you
Who the users are and what they do today, which systems exist, what must be in the first version and what must not, and who decides. If a document already exists, it is the starting point.
- 2
Decision meetings
A short meeting at the end of each stage: what was found, what was decided, what is open. Decisions are written down so the next stage does not reopen them.
- 3
Review rounds
Each deliverable goes through an agreed review round. Flow comments are closed at wireframe stage; appearance comments at design stage. Mixing the two is what drives cost up.
- 4
Scope approval
Before moving to UI design or development, the list of screens and scenarios is approved in writing. A change after approval is a scope change — priced and documented, not absorbed.
A deliverable example
To see what a filled-in requirements document looks like — users, scenarios, screens and acceptance criteria — we published a complete educational example (not a client project), with a downloadable template.
How does this continue into development?
Deliverables are handed over so that any development team can work from them — ours or another. If you continue with us, the designer stays on the project; if not, our responsibility ends at the documented handoff and implementation questions move to the development vendor.
// 06 · Who it's for
Who this is for
- 01
Startups
Who need a well-designed MVP — because you don't get a second chance to make a first impression.
- 02
SaaS companies
That need a redesign of an existing product — to improve conversion and retention.
- 03
Businesses with legacy products
Old websites or systems that need a visual and experiential upgrade.
- 04
Organizations needing a design system
To enable consistent work across multiple teams — without every team reinventing the wheel.
- 05
Founders with an idea
Who need a prototype to show investors — a real product that feels alive, not a slide deck.
// 07 · Why us
Why us
- 01
Designers who understand product
Not just "illustrators." We think in the language of product and business.
- 02
Designers who know engineering
Everything we draw can actually be built. No unpleasant surprises.
- 03
Full team under one roof
UX designer, UI designer, user researcher. All in-house, in sync, without middlemen.
- 04
Flexibility
Order design only, development only, or both. We adapt to what you need.
// 08 · FAQ
Frequently asked questions
01.What's the difference between UX and UI?
UX is how it works. UI is how it looks. UX starts before there's even a screen — what's the flow, what are the needs. UI designs the screen itself. They work together.
02.How much does UX strategy and UI design cost?
It depends on scope. UX strategy for a marketing site — ₪8-20K. Full UX for an app or system — ₪20-60K. UI design starts at ₪12K for a marketing site and scales with complexity.
03.How long does design take?
A marketing site — 2-4 weeks. An app — 4-8 weeks. A full SaaS product — 2-4 months. Depends on the number of screens and complexity.
04.Do you do user research?
Yes. Interviews, surveys, usability testing. We recommend it for projects that justify it. Without research, you're designing on guesses.
05.Do you design for both Hebrew and English?
Yes. RTL and LTR from day one. Including typography — not every Hebrew font pairs well with every English font. We know how to match them.
06.Can I order design only, without development?
Absolutely. Many of our clients order design only and develop in-house or with another team. We provide a full, professional handoff.
07.Do you work with our existing design system?
Yes. If you have a design system, we work inside it. If you don't, we build one from scratch or extend what you have.
08.What if I disagree with your design?
Totally fair. Design is a process. There are revision rounds at every stage, and we explain the reasoning behind every decision. You see the why — not just the what.
09.Do you also build interactive prototypes?
Yes. In Figma or Framer. Great for investors, user testing, and understanding how the product will feel.
10.Do you start from scratch or build on what's there?
Both. We audit what exists, find the problems, and recommend either a partial upgrade or a full redesign.
11.What about accessible design?
We design to EAA and WCAG 2.2 AA from the start. Accessibility isn't a bolt-on at the end — it's design decisions from day one.
Last reviewed:
Related reading
Guide
App requirements document example — a filled-in template to download
What to define before asking for a quote: users and permissions, flow and states, scope and exclusions, screens with failure states and acceptance criteria. Includes a Word file to work in.
Case study
Case study: Michrazit — order in the private-construction jungle
A two-sided tender platform: transparent comparison, vetted suppliers, digital contract. Modern web architecture with a clear path from tender to signed deal.
Case study
Case study: Tory — on-demand mobile services
We built a client app, a driver app, and a real-time dispatch backend from scratch. Architecture, matching engine, and an order flow measured in seconds.
// 09 · Let's talk
Got a product that needs a rethink?
A 30-minute intro call. No strings attached. We'll look at the product, point out the weak spots, and decide together if it's worth moving forward.
Less. Simpler. Clearer.