Your website should do more than look good. It should bring you business.
I build conversion focused websites and digital systems that turn online attention into customers, bookings, inquiries and sales. One builder, accountable start to finish.
Most business websites are brochures pretending to be salespeople.
It says what you are, not what you fix
A visitor decides in a few seconds whether you solve their problem. Most sites spend those seconds on a welcome message.
The next step is hidden
Someone ready to book has to hunt for how. Every extra tap between wanting and doing loses people who were already sold.
It falls apart on a phone
Most of your traffic arrives on mobile, often inside Instagram's own browser. That is exactly where most sites were never tested.
Is your website actually working?
I will look at your website the way a customer would. Messaging, mobile experience, trust, calls to action, booking flow, speed, and everything between the first click and the next customer.
You get a written breakdown of what is working, what is losing you business, and what I would change first. No pitch deck, no pressure.
What I build.
Websites that work as hard as you do.
Custom sites built around the path from stranger to customer, not around a template someone else designed for a different business.
Find out why it is not producing.
You already have a site and it is not bringing business. I work out where people are giving up, then rebuild around what they actually do.
Turn attention into inquiries.
Traffic that does not convert is noise. This is the machinery that captures it and routes it somewhere you actually check.
The front desk, not the brochure.
Booking with deposits, payments, business email, analytics and the integrations that hold the whole operation together.
Meta campaigns, run properly.
Facebook and Instagram setup, creative, targeting and optimization. You pay spend directly to Meta, so you always see what goes where.
Equipment, not furniture.
Updates, maintenance, performance checks and ongoing optimization, so the site does not quietly rot the month after launch.
Four businesses, four different problems.
Screenshot pendingBraids by Tosin
Bookings lived in Instagram DMs. Now the site takes the appointment, holds a deposit, and emails the client without anyone typing a reply.
Read the case study
Screenshot pendingO.G.A
An artist whose entire audience arrives from social media, through browsers that quietly break most independent links.
Read the case study
Screenshot pendingWami
Street vendors are real businesses that no map can find. Wami is the platform that makes them discoverable.
Read the case study
Screenshot pendingKa Frika
African food import and wholesale, plus the logistics software running fleet, inventory and traceability behind it.
Read the case studySix steps, and you know where you are in all of them.
Audit
I look at what you have now, or at what your competitors have if you have nothing yet, and identify where business is being lost.
Strategy
We agree what the site has to achieve. Bookings, inquiries, orders, applications. Everything after this is measured against that one goal.
Design
You see the direction before anything is built. Visual identity, structure, and the path a customer takes through it.
Build
I write it. Front end, backend, database, integrations, email, payments. You talk to me the whole way, not to a project manager.
Launch
Domain, hosting, analytics, testing on real phones and inside social media browsers. Then the keys go to you.
Grow
Care plan, ongoing optimization, and advertising if you want it. Only because it is working, never because you are locked in.
You get the builder.
- No relay chain
- No account manager passing your notes to a designer who passes them to a developer. You talk directly to the person writing the code, so nothing gets lost in translation and nothing waits a week for a meeting.
- One person accountable
- I build the website myself, every time. When a project needs something outside what I do, photography or video for example, I bring in someone I have worked with and vouch for, and I stay responsible for their work. You get one point of contact either way.
- Built without the overhead
- You are paying for the work, not for an office, a sales team and four layers of management. That is why a premium build here does not carry an agency price tag. Affordable is not the same thing as cheap.
- You own everything
- Code, accounts, domain, database, infrastructure, all in your name. I build it, launch it, and hand you the keys. If you want to work with someone else next year, nothing stops you.
- Built for the real world
- Sites break in specific places. Inside Instagram's browser, on an old phone, when a payment processor decides a new business looks suspicious. Those get checked before launch, not after a customer complains.
- 30 day build guarantee
- If something is broken because of how I built it, I fix the defect. Ongoing changes and improvements go through a care plan, so you always know what is covered and what is not.
Three ways in.
Starting figures. What a project costs depends on how much of the business the software has to carry.
For a business that needs a credible presence and a contact path that works.
- Focused site structure
- Responsive design
- Contact form
- Basic SEO foundation
- Social integration
- Analytics
- Domain and launch assistance
For a business where the website has to do the work, not just describe it. Strategy, custom design and real business systems.
- Multi page conversion architecture
- Custom design
- Conversion focused structure
- Lead capture and inquiry flow
- Booking functionality
- Professional business email
- Performance optimization
- Client training at handover
For a business building a complete digital operation, with conversion strategy and advertising infrastructure behind it.
- Full site architecture, scoped to your business
- Bespoke design and brand direction
- Advanced conversion strategy
- Lead generation systems
- Advanced integrations
- Landing pages
- Ad ready infrastructure
- Priority support
Businesses, not brochures.
Every project here solved a specific operational problem for a specific person. Where a project is still in build, it says so.
Built for someone else's business.
Screenshot pendingBraids by Tosin
Studio site with a real booking backend, deposit handling, automated client email and a private admin screen.
Read the case studyScreenshot pendingO.G.A
Artist site engineered to open correctly inside social media browsers, where most independent musician links fail silently.
Read the case studyBuilt because the thing did not exist.
Screenshot pendingWami
A discovery platform for mobile vendors, the food carts and pop ups no map has ever bothered to track.
Read the case studyScreenshot pendingKa Frika
African food import and wholesale, with custom software handling fleet, intake, inventory and traceability.
Read the case study
Screenshot pendingKojoda
The booking system from Tosin's site, rebuilt as software any studio can sign up for and embed on their own page.
Read the case study
Screenshot pendingWoEta
Navigation for delivery drivers that answers the question maps refuse to answer: which door do I actually walk to.
Read the case studyBuilt to run the other work.
Not public products. They exist so client projects stay efficient and organised, and they are described without live links because they hold client credentials.
Ọ̀nà ụzọ
Routes custom email addresses for client domains, so a client gets hello@theirbusiness.com without a monthly mailbox bill per address. Tokens encrypted at rest, each client isolated in their own account.
Ọkọ̀
The logistics layer behind Ka Frika. Offline first, because a warehouse basement and a loading dock are two of the worst places on earth to have signal.
The studio that stopped losing bookings in the DMs.
Braids by Tosin did not need a website. It needed the part of the business that happens between someone deciding to book and someone sitting in the chair.
The problem
Braiding appointments were arriving through Instagram messages. That works until it does not. Two people ask for the same Saturday. Someone books a style that needs six hours into a four hour gap. A client who never paid anything simply does not turn up, and that chair sits empty on the busiest day of the week. The business was real. The system around it was a phone and a good memory.
The opportunity
Every no show is a full appointment slot of revenue that was never going to be recovered. Every unanswered message overnight is a client who booked somewhere else by morning. And every hour spent answering the same question about what hair to buy is an hour not spent braiding. Fixing the booking process was not a cosmetic upgrade, it was the highest value change available to the business.
The build
A multi page site where every page has a job. Services with honest starting prices and the hair each style needs. A gallery that does the persuading. A booking flow that captures the appointment properly, takes a deposit so the slot means something, and confirms by email without anyone typing a reply.
Behind it, a database holding services, appointments, clients and intake answers. Automated email at the three moments that matter: confirmation, reminder and follow up. A private admin screen behind a PIN so the studio can see the day at a glance without touching a database.
The experience
A client arrives from Instagram, on a phone, usually inside Instagram's own browser. She sees the work, finds the style she wants with its real starting price and hair requirement, picks a time, pays a deposit, and gets a confirmation email before she has closed the tab. She never has to ask a question the page could have answered.
- Prices shown as starting figures, because braid pricing genuinely depends on length and density and a fixed number becomes an argument in the chair.
- Hair requirements labelled on every service, since that was the most common pre appointment message.
- The deposit is a commitment signal, not a payment gate. It exists to reduce no shows.
- The whole flow was tested inside Instagram's in app browser before launch, because that is where the traffic comes from.
The result
Bookings now arrive as structured appointments with deposits attached instead of as messages that need chasing. Confirmations and reminders go out on their own. The studio can see its whole week without scrolling a DM thread.
Measured booking and no show figures since launch: Metric pending
The artist link that actually opens.
Independent musicians lose listeners to a problem nobody warns them about. The link works fine when they test it, and breaks for everyone who taps it inside Snapchat.
The problem
An artist page has one job: move a person from a social post to a streaming platform without losing them on the way. Almost all of that traffic arrives through an in app browser inside Instagram, Snapchat or TikTok. Those are not Safari and not Chrome, and they break things in ways that never appear when you test on a laptop. On top of that, a brand new domain with a music page and outbound links pattern matches to exactly the kind of site automated scanners flag as suspicious.
The opportunity
Every listener who taps a link and hits a broken page is gone permanently, and the artist never finds out it happened. There is no error report for a fan who gave up. Fixing compatibility is not a technical nicety here, it is the difference between a post converting and a post disappearing.
The build
A single page, which is the one situation where a single page is correct, because the entire purpose is to move people out to platforms rather than deeper into the site. A leopard splash with a claw slash animation on entry. Platform tiles for Spotify, Apple Music, Audiomack and YouTube pointing at real releases. Email capture, a contact form, and a light and dark toggle.
The experience
A listener taps a link in a story. The page opens inside the app's own browser, loads immediately, and gives them four obvious ways to hear the music on whatever platform they already use. No redirect chain, no security warning, no blank screen.
Most of the work was invisible. Several iOS Safari and Snapchat failures were diagnosed and fixed, covering how those browsers handle canvas, autoplay and outbound navigation. Then the site was reviewed adversarially: how does this look to Google Safe Browsing, to Meta's scanner, and to a first time visitor deciding in two seconds whether this is real.
That adversarial review is now standard on everything I build. It started here.
The result
The link opens correctly in the environments the audience actually uses, with analytics running quietly in the background so the artist can see which platform converts.
Public URL: URL pending · Platform click through figures: Metric pending
The vendors the map forgot.
Every map application assumes a business has a fixed address. Street vendors do not. Wami is the platform built for the part of a city that moves.
The problem
A food cart, a pop up, a truck that parks on a different corner depending on the day. These are real businesses with real customers, and they are invisible to every discovery tool we have, because those tools were built around a fixed street address. The customer cannot find the vendor. The vendor cannot be found. Both sides lose, quietly, every single day.
The opportunity
Vendors currently depend entirely on foot traffic and luck. A vendor who can be found on purpose rather than by accident sells more of the same food from the same cart. That is the whole business case, and it is why this is a marketplace rather than a directory.
The build
A two sided platform. Vendors mark where they are and what they have today. Customers find what is near them right now, not what was near them last Tuesday. Launching in Baltimore, because a hyperlocal product without local density is just an empty map.
Revenue comes from a vendor subscription for tools that help vendors sell more, an ad supported free tier framed as community support rather than interruption, a daily check in streak where forgiveness is earned through real transactions instead of bought, and cosmetic personalisation, which people buy once they feel ownership of a place.
The experience
The line the whole brand sits on is this: Wami does not show you the city, it remembers you in it. The product is not really search. It is the feeling of a place knowing you, of the man at the cart starting your order before you speak. The software is trying to reproduce that at city scale.
The result
In active build. The marketing site is live at getwami.com. Vendor onboarding and the launch cohort are the current work.
Vendor and user figures at launch: Metric pending
Importing food is mostly paperwork.
Ka Frika brings West African staples into the United States wholesale. Building it meant learning that the hard part is not shipping. It is the regulation.
The problem
Wholesale buyers do not order from a vague website. They want to know the grade, the growing area, the origin, and whether you can supply the same thing again next month. Generic product listings lose those buyers in the first thirty seconds, because a buyer who cannot verify what they are getting assumes you cannot supply it reliably.
The opportunity
Specificity is the entire sales argument in wholesale food. A site that names the growing area of each rice grade is not showing off, it is proving the supply chain exists. That proof is what converts a browsing buyer into a purchase order.
The build
An eight page site with real product depth: four grades of ofada rice separated by growing area, three distinct garri traditions rather than one generic entry, and a full SKU list with region specific origin markers. Home, Marketplace, Journey, About, Gallery, Our Network, Partner and Contact, each carrying a different part of the buying decision.
Alongside it, a logistics application handling fleet, bulk intake, inventory, partners, communications and traceability. It is offline first, because loading docks and warehouse basements are exactly where phone signal disappears.
The experience
A buyer lands, finds the exact grade they source, sees where it comes from, and reaches a partner enquiry without hunting. Internally, intake and inventory are recorded on a phone at the dock and sync when signal returns, rather than being written on paper and re entered later.
The result
The original product plan included frozen goat, oxtail and ponmo. Under current USDA eligible country rules those cannot be imported from West African origins, and building a marketplace around products the business is not permitted to sell would have been a serious problem discovered far too late. It was caught during the build and the catalogue was rebuilt around what is actually importable.
That is the part of the work that does not look like web development and matters more than most of the work that does. Site built, compliance groundwork in progress across entity registration, FDA facility registration, foreign supplier verification and a customs bond.
One studio's booking system, rebuilt for every studio.
After building the booking machinery for Braids by Tosin, the obvious question was why the next studio should pay for it to be built from scratch again.
The problem
Braiders, barbers and nail technicians all lose money to the same three things: double bookings, no shows, and hours spent answering identical questions by message. Each of them solves it alone, badly, with a notebook and a calendar app that does not take deposits.
The opportunity
Tosin's site solved this for one studio. The solution is not specific to braiding, it is specific to appointments with deposits. Every studio that installs it gets back the same hours and the same no show revenue, without paying for a custom build.
The build
- A full appointment lifecycle, with deposit states handled as a proper state machine rather than a single yes or no, because half paid, refunded and forfeited are genuinely different situations that need different behaviour.
- Timed email at each stage, with tokenised reschedule links so a client can move an appointment without messaging anyone.
- An intake question builder, so each studio asks what it actually needs to know before the client arrives.
- Widget theming and an embeddable script, so the booking flow looks like the studio's brand rather than a third party tool bolted on.
The experience
A studio owner signs up, sets their services and questions, pastes one line into their existing site, and starts taking deposits. Their clients never see Kojoda's name.
The result
Scaffolded and in build. Remaining before the first tenant: database migrations, email functions deployed, and production hosting.
The pin is on the building. The door is not.
Delivery navigation ends at a coordinate. The driver's job ends at a door. WoEta is about the gap between those two things.
The problem
Every delivery driver knows the address that drops you on the wrong side of a building. The loading entrance is around the back, the apartment lobby is on the other street, the complex has exactly one gate that opens. Navigation apps do not know any of this, so every driver relearns it individually, forever, one wasted trip at a time.
The opportunity
Minutes lost per stop compound across a shift. A driver who knows which door to walk to before arriving completes more deliveries in the same hours. The knowledge already exists, it is just trapped in individual drivers' heads.
The build
Turn by turn navigation with toll avoidance, built on open mapping infrastructure rather than a metered commercial API, so running cost does not scale painfully with the number of drivers.
On top of that, the actual product: crowdsourced entrance intelligence. Drivers mark where the real door is, and the next driver arrives knowing. Contributions carry a reputation system with four ranks, because entrance data is only useful if it is trustworthy, and trust needs a way to be earned and lost.
The experience
A driver approaches a stop and sees not just the address but the entrance another driver confirmed, with the confidence attached to who confirmed it.
The result
In build. An API audit was run before building to confirm every external service could carry the load at the intended cost, and a thirteen point code audit was run after. Building on efficient infrastructure only works if you verify the limits before depending on them.
Everything between a visitor and a customer.
You are not buying pages, databases or frameworks. You are buying the result those things produce. Here is what I build and what each one is actually for.
Have a site already and want it reviewed first? Request an audit →
- Websites
- A custom site built around the path a customer takes, from the first line they read to the moment they book, call or buy. Every page has a job and every page leads somewhere. Designed for your business specifically, so it does not look like eleven other sites in your city.
- Website redesign
- You already have a site and it is not producing. I find out why. Usually it is messaging that describes instead of persuades, a contact process with too many steps, or a mobile experience nobody checked. Then I rebuild around what customers actually do.
- Lead generation
- Traffic that does not convert is just noise. This is the machinery that captures it: inquiry forms that ask the right questions, lead capture that respects people's time, routing so nothing sits unanswered, and follow up email that goes out whether or not you remember.
- Business systems
- Booking and appointments with deposits and reminders. Professional email on your own domain. Payments. Analytics you can read. Integrations between the tools you already use. This is the part that turns a website into the front desk of the business.
- Meta advertising
- Facebook and Instagram campaign setup, creative, targeting, monitoring, optimization and reporting. You pay your own ad spend directly to Meta. I charge separately for setup and monthly management, so you always know what goes to the platform and what goes to me. I do not promise guaranteed sales or revenue. Anyone who does is guessing.
- Website care
- Content updates, technical maintenance, performance checks, small design changes and support. A website is not furniture, it is equipment, and equipment needs someone looking after it. Care plans start at $39 per month and scale with the size of the build.
The technical part exists so the business part works.
You should not have to care about any of this. But it is the reason one person can deliver a complete system instead of just a design file.
The parts people forget to ask about.
- Trust review
- Before anything launches I look at it the way an automated scanner does. Google Safe Browsing, Meta, Snapchat and payment processors all make automated judgements about new sites, and a legitimate business can get flagged for structurally resembling a scam. Getting unflagged is far harder than not getting flagged.
- Social browser testing
- A large share of your traffic will open your link inside Instagram or Snapchat rather than Safari or Chrome. Those built in browsers behave differently and break things quietly. Every site gets tested there.
- Ownership handover
- Accounts in your name, a written explanation of how everything works, and a walkthrough. You should be able to run your own business without calling me.
- Honest scoping
- If what you need is smaller than what you asked for, I will tell you before you pay for it. If it is bigger, I will tell you that too.
Clear numbers, before you ask.
Three tiers and three care plans. Every build includes strategy, mobile optimization, analytics, launch support, a trust review, and full ownership handover.
These are starting figures, not menu prices. What a project costs depends on how much of the business the software has to carry, so the final number comes after we talk about what you actually need.
For a business that needs a credible presence and a contact path that works.
- Focused site structure
- Responsive design
- Contact form routed to your inbox
- Basic SEO foundation
- Social integration
- Analytics
- Domain connection assistance
- Launch assistance
Minor updates, small content changes, technical monitoring, basic support
For a business where the website has to do the work, not just describe it. Strategy, custom design and real business systems.
- Multi page conversion architecture
- Custom design
- Conversion focused structure
- Mobile optimization
- SEO foundation
- Analytics
- Professional business email and signature
- Lead capture
- Booking or inquiry functionality
- Performance optimization
- Domain setup and launch assistance
- Client training at handover
Updates, content changes, maintenance, performance checks, minor design changes, conversion recommendations
For a business building a complete digital operation, with conversion strategy and advertising infrastructure behind it.
- Full site architecture, scoped to your business
- Bespoke design and brand direction
- Advanced conversion strategy
- Advanced SEO foundation
- Analytics and tracking
- Professional email
- Lead generation systems
- Booking and contact systems
- Advanced integrations
- Landing pages
- Ad ready infrastructure
- Priority support and launch strategy
Extensive ongoing support, optimization and conversion work
Not pages. Judgement.
Anyone can add a page. The value is in knowing which pages should exist, what each one has to do, and what happens after somebody clicks.
- Strategy
- Working out what the site has to produce before a single screen gets designed, then measuring every decision against that.
- Design
- A visual identity built for your business specifically, so it does not look like eleven other sites in your industry.
- Development
- Front end, backend, database and integrations, written by the same person who designed it.
- Conversion architecture
- The route from a stranger landing to a customer committing, designed deliberately rather than assembled by accident.
- Business systems
- Booking, deposits, payments, email, analytics. The machinery that turns a website into the front desk.
- Launch and handover
- Domain, hosting, trust review, real device testing, and the keys handed to you with an explanation of how it all works.
Priced separately, on purpose.
Ad management is not bundled into a build package, because a build finishes and advertising does not. Bundling it would either shortchange you or bankrupt me.
- How it is structured
- Website build first, then advertising setup as a one time fee, then monthly campaign management. You pay ad spend directly to Meta, so you always see exactly what the platform is charging you.
- What management covers
- Creative, targeting, campaign monitoring, optimization and reporting. Quoted after we talk, because a campaign for a braiding studio and a campaign for a wholesale importer are not the same job.
- What it does not include
- Guaranteed sales, guaranteed revenue, or a promised return. Anyone quoting you those numbers upfront is guessing, and you should treat that as information about them.
How payment and protection work.
- 50 percent deposit
- A deposit reserves your project and starts the build. The remaining balance is due before launch. This keeps the schedule honest on both sides.
- 30 day build guarantee
- If something is broken because of how I built it, I fix the defect at no cost within 30 days of launch. This covers defects, not new features or changes of direction. Those are what care plans and change requests are for.
- Care is optional
- You are never required to take a care plan, and cancelling one does not take your website away. You own it. The plan exists because most businesses would rather someone else handle updates.
- Custom work
- Projects beyond these packages, full products, multi tenant software, complex integrations, are quoted individually after a conversation.
Is your website actually working?
Most business owners have never seen their own site the way a stranger sees it on a phone, in a hurry, deciding in four seconds whether to bother. I will show you.
This is for businesses that already have a website. If you need one built, start a project instead. You do not have to be audited first.
Twelve things, in the order a customer meets them.
Messaging
Does the first thing a visitor reads tell them you solve their problem, or just tell them your name?
Trust
Does this look like a real business someone can safely give money to, within the first few seconds?
Mobile experience
How it behaves on an actual phone, including inside the Instagram and Facebook in app browsers.
Navigation
Can someone find what they came for without thinking about it, or do they have to explore?
Call to action placement
Is the next step visible at every moment somebody might be ready to take it?
Conversion path
The full route from landing to becoming a customer, counted in steps and drop off points.
Contact process
How many taps to reach you, and where the message lands once it is sent.
Booking process
Whether someone can commit at the moment they decide to, or has to wait for a reply first.
Social integration
Whether traffic from your social accounts arrives somewhere that continues the conversation.
Performance
Load speed on a normal phone connection, not on office wifi.
SEO fundamentals
Whether the basics are in place for people searching for what you sell.
Overall journey
The whole thing end to end, and the single change that would make the biggest difference.
A written breakdown, not a sales call.
What is working
Because some of it is, and you should not change those parts.
What is costing you
The specific places a ready customer gives up, with the reason each one loses them.
What I would fix first
Ranked by impact, not by how much work it would be for me. Some of it you can do yourself.
If the fix is worth hiring someone for, I will tell you what that would look like. If it is not, I will tell you that instead. No business owner has ever been persuaded by someone insulting their website.
Tell me where to look.
Takes about two minutes. The last two questions are the ones that make the audit actually useful, so spend your time there.
Let's build your website.
Tell me what your business does and what you need it to do. You do not need to know what should be built. That part is my job.
What are you starting?
This just sets the first question. You can change it in the form, and if none of them fit, the last one is a real answer.
You have a business and no site, or one you would rather start over than repair.
Start here → A redesign.The site exists, it looks dated or it is not producing, and you want it rebuilt around what customers actually do.
Start here → The machinery behind it.Booking with deposits, payments, business email, automated client email, a private admin screen. The operational part.
Start here → A full product.Something that does not exist yet. Multi tenant software, a platform, an internal tool with a real database behind it.
Start here → Advertising only.The site is fine. You want Meta campaigns set up and managed properly, with reporting you can read.
Start here → Honestly, I am not sure.You know something is not working but not what to do about it. Let me look at what you have and tell you. Free, no obligation.
Request an audit instead →Tell me about it.
Four steps, about three minutes. The more you put in, the closer my first reply is to an actual plan instead of a list of questions.
Not ready for this? Request a free audit instead →
Just have a question? Ask me anything →
Let's talk.
Whether you already know what you need or you are still figuring it out, start here. Pick whichever one sounds like you.
I will look at your current site and identify where the customer experience and conversion path are losing you business.
Request an audit I need a website.Tell me about your business, what you are trying to accomplish, and what you need built. No audit required first.
Start a project I have a question.Not ready to start anything? That is completely fine. Ask, and I will get back to you.
Ask a questionAsk me anything.
Pricing, timelines, whether I can build a particular thing, or something else entirely. No commitment attached to asking.
Joseph Adewumi.
Olúwagbémilékẹ́.
I build websites and digital systems for businesses out of Baltimore. Alone, mostly, and on purpose.
Why one person
Agencies lose things in the handoff. The designer does not know what the database can do, the developer does not know what the client actually meant, and the client ends up paying for the translation between them. When one person does the whole build, the design already accounts for the backend and the backend already accounts for what you said in the first meeting.
The trade off is honest: I take fewer projects at a time. That is the deal, and it is why the work does not feel like it came off a production line.
Why conversion comes first
A beautiful website that nobody acts on is an expensive picture. Before anything gets designed I want to know what the site is supposed to produce, whether that is bookings, calls, orders or applications. Everything after that gets judged against it. If a section looks incredible and moves nobody closer to becoming a customer, it comes out.
What I actually do all day
React, Vite, Tailwind, Supabase and Netlify are the working stack for most builds, chosen because they are fast to build in and efficient to run. Your business should not inherit infrastructure costs designed for a company a thousand times its size.
Beyond code, a lot of the job is the unglamorous part: FDA registration rules for a food importer, deposit and refund logic for a studio that gets no shows, whether a payment processor will accept a new business in a given category. Software that ignores the regulation around it is not finished software.
Where the name comes from
There is a small mark at the bottom of every site I build. Made by Joseph, with a heart. It started as a signature and turned into how most of my work arrives, because someone sees a site they like, scrolls to the bottom, and clicks. This site is that mark, opened up.
The rest of it
I studied Management Information Systems and Construction Management, which is a strange pair until you notice both are about making a complicated thing get built correctly by a specific date. I make music as O.G.A. Most of my product names are Yoruba, because naming a thing in the language it came from is not decoration, it is accuracy.
Got it. Thank you.
Your message is with me. I read every one myself, and you will hear back from me directly rather than from an autoresponder pretending to be a team.