# Abdelrahman Elgendy

> Freelance web designer and developer. Certified Webflow developer, Top Rated on Upwork. Designs and builds websites end to end, mostly in Webflow, some in Framer, usually starting from a Figma file.

One person, not a studio or an agency. There is no team.

## How to get in touch

There is no email address and no contact form on this site, by choice. Two routes only:
- Upwork (primary, handles contract and escrow): https://www.upwork.com/freelancers/abdelrahmanelgendy
- LinkedIn: https://www.linkedin.com/in/abdelrahman-gendy/

## Pages

- [Home](https://www.webgendy.com/): who he is and what he does
- [Work](https://www.webgendy.com/work): the case studies
- [About](https://www.webgendy.com/about): the longer version, first person

## Work

### Erin Tunney
- URL: https://www.webgendy.com/work/erin-tunney
- Sector: Luxury real estate, Nashville
- Scope: Design and build
- Built with: Webflow, Webflow CMS, Local SEO
- Live site: https://erintunney.com
- Summary: A Nashville real estate brand built around a listings engine her team runs without calling a developer.
- Erin sells property in Nashville and came to me to rebuild her site. Two things shape everything else on a project like this. A listing is judged in about as long as it takes to scroll past it, so the photography has to be the loudest thing on the page. And a site an agent cannot update herself stops being current the week after it launches. So the site is modeled as content rather than as pages: listings, neighborhoods and posts are all collections, and putting a new one up is filling in a form.

### Teed & Brown
- URL: https://www.webgendy.com/work/teed-and-brown
- Sector: Lawn care and irrigation
- Scope: Design, build and SEO
- Built with: Webflow, Local SEO, Technical SEO
- Live site: https://teedandbrown.com
- Summary: A lawn care company that sells town by town, given a page for every town it actually serves.
- Teed & Brown treat lawns and irrigation systems across New York, Connecticut and New Jersey. Work like this is bought locally: somebody searches for lawn care in the town they live in, and a single page listing thirty place names is not an answer to that search. So the service areas are real pages. Each town has its own URL with its own state in the path, which is the difference between a site that shows up in a town and a site that merely says it covers one.

### Lumofy AI
- URL: https://www.webgendy.com/work/lumofy
- Sector: B2B SaaS
- Scope: Figma to Webflow
- Built with: Webflow, Figma to Webflow, Design systems
- Live site: not linked. The site online today is a later rebuild by someone else, so it is not evidence of this work.
- Summary: A workforce performance platform with a long product story to tell, built page by page from Figma.
- Lumofy is a workforce performance platform, which means the site has a long story to tell before anyone gets to a pricing page: what the product does, who inside a company it is for, and what it connects to. The design arrived as a Figma file, and my job was to build it in Webflow without the usual erosion, where a handoff loses its spacing, its type scale and half its states somewhere between the artboard and the browser.

### Bayty Trading
- URL: https://www.webgendy.com/work/bayty-trading
- Sector: B2B import and export
- Scope: Design and build
- Built with: Webflow, Web design, Technical SEO
- Live site: https://baytytrading.com
- Summary: A food commodities trader whose website is the only due diligence most buyers do before making contact.
- Bayty trade food commodities internationally: salt, flour, pasta, spices. In this market the website is often the only checking a buyer does before deciding whether to make contact at all, and the order sizes are large enough that any doubt ends the conversation silently, without a reply to read. So the site answers three questions in the order a buyer asks them. What do you trade, to what standard, and who do I speak to. This was the second project I built for them.

### CodeContent
- URL: https://www.webgendy.com/work/codecontent
- Sector: Technical content agency
- Scope: Website and CMS blog
- Built with: Webflow, Webflow CMS, Technical SEO
- Live site: not linked. The site online today is a later rebuild by someone else, so it is not evidence of this work.
- Summary: An agency that sells publishing, given a blog its own writers could actually publish to.
- CodeContent pair engineer-writers with developer tools companies, which means their own blog is not a marketing extra, it is the proof. An agency that sells publishing gets judged on how often it publishes, and a quiet blog is worse than no blog at all. The obstacle is almost never willingness, it is friction: when putting a post up means wrestling a layout, the cadence slips inside a month. So the build put its effort into making publishing the easy path.

## How a project runs

### 01. Discover & Plan
It starts with a conversation about what the site is actually for: who you are selling to, what has to happen on the page, and which of those things matters first. A full site, a landing page, a blog and a store need different decisions, and making them now is what stops the scope moving later.

### 02. Design & Build
I do both, so nothing gets lost being handed between two people. Responsive from the first breakpoint rather than patched afterwards, with the CMS modeled around the content you will really be adding, and the search groundwork laid while the structure is still cheap to change.

### 03. Launch & Optimize
Before it goes live I go through it properly: speed, every breakpoint, the forms, the links, the things that only break on a real phone. Content gets loaded, the SEO basics get set up, and the last round of refinements happens before launch rather than after someone else finds them.

### 04. Maintain & Grow
A site is not finished at launch, it just stops changing. I stay available for edits, updates and the improvements that only become obvious once real people are using it, so the site keeps up with the business instead of dating quietly.

## Tools

### Where I build
Webflow is where most projects land, and the one I am certified in. It is what gets a client a site their own team can run afterwards. Framer covers the work that sits closer to the design file, where launching quickly matters more than a deep content model.
Tools: [object Object], [object Object]

### How designs arrive
Most projects start as a Figma file, sometimes mine and often somebody else's. Translating one into a built site without losing its spacing, its type scale or half its states is the part that takes the care, and it is most of the job on a handoff.
Tools: [object Object], [object Object]

### What I write by hand
Visual builders stop somewhere, and the interesting part of a brief is usually just past that line. Custom markup, styling and scripting go in where the platform runs out, which is a deliberate decision each time rather than a default setting.
Tools: [object Object], [object Object], [object Object]

## Claims and their basis

- Certified Webflow Developer, Top Rated on Upwork, CSS Design Awards and an Awwwards feature are all verifiable on the relevant public profile.
- "100+ sites shipped" is his own figure. It is a count of work done, not a rating and not a client satisfaction claim.
- There are no performance metrics anywhere on this site. No traffic percentages, no conversion lifts, no rankings. Nothing of that kind was verifiable, so nothing of that kind is claimed.
- The testimonials are reproduced verbatim, with names and roles as given. There is no star rating attached to any of them, because none was supplied.