Most projects start in one of these and end up touching all of them. That is the point of not splitting them across companies.
Most projects start in one of these and end up touching all of them. That is the point of not splitting them across companies.
Deciding what the thing actually is.
What it does, who for, and — harder — what it refuses to do. Meetzy opens on mood rather than a category list because of a decision made here, before anything was drawn.
- Definition
- Scope
- Prototyping
- Cutting
A claim on its own is worth nothing. Each row here runs from a problem someone actually has to the thing on this site that shows it can be solved.
| Problem | Product type | System | Capability | Example |
|---|---|---|---|---|
| There is a product in your head and nothing on a screen yet | A new product | DefinitionPrototypeClientBackendRelease | Product development | MeetzyShippedWent from a single observation to a live app with around 2,000 signups, built by one person. |
| The work happens in a browser and needs accounts, data and permissions | Web application | FrontendBackendDatabaseAuthenticationAdmin | Product development | DivanConceptA full web application with roles, records and reporting, running here. |
| It has to be on a phone, in someone's pocket, wherever they are | Mobile product | Mobile clientBackendDatabaseNotificationsMaps | Product development | MeetzyShippedLive on phones for about three months. The screens on this site are captures of it. |
| The company runs on spreadsheets, messages and one person who remembers everything | Internal system | RecordsStatesRolesApprovalsReporting | Business software | AtölyeConceptJobs, schedules, materials and approvals — the spreadsheet, written down properly. |
| You are selling, and the storefront is the smaller half of the problem | Commerce system | CatalogueStockCheckoutPaymentsOrdersAdmin | Commerce | Erden DavetiyeShippedA live storefront and the admin an atelier in Ankara actually runs on. |
| There is a model that could help, and no safe place to put it yet | AI inside a process | RetrievalGroundingConfidenceApprovalAudit | AI | UlakConceptDocuments read into typed fields, thresholds that decide when not to answer, every run traceable. |
| The same handful of tasks is done by hand, every day, by people who could be doing something else | Automation layer | TriggersConditionsApprovalsIntegrationsAudit | Automation | VardiyaConceptRules a support lead can change, and a handover to a person the moment the ground runs out. |
| It works, and nobody can say which part of it is working | Measurement and extension | EventsFunnelsCohortsReportsIntegrations | Data | ÖlçekConceptEvents modelled properly, so the question you have in six months is a query rather than an export. |
| People need to find something, get in, and be counted at the door | Event technology | DiscoveryTicketingCheck-inAttendeesReporting | Product development | MeetzyShippedLive, and built around the half of this problem nobody solves: finding someone to go with. |
| Nothing off the shelf fits, and the parts that do not fit are the parts that matter | Custom software | Whatever the problem needsModelled firstThen built | Custom software | KervanConceptTwo applications, one ledger, split orders and derived payouts — the hardest shape in this collection. |
There is a product in your head and nothing on a screen yet
- Product type
- A new product
- Capability
- Product development
- System
- DefinitionPrototypeClientBackendRelease
The work happens in a browser and needs accounts, data and permissions
- Product type
- Web application
- Capability
- Product development
- System
- FrontendBackendDatabaseAuthenticationAdmin
It has to be on a phone, in someone's pocket, wherever they are
- Product type
- Mobile product
- Capability
- Product development
- System
- Mobile clientBackendDatabaseNotificationsMaps
The company runs on spreadsheets, messages and one person who remembers everything
- Product type
- Internal system
- Capability
- Business software
- System
- RecordsStatesRolesApprovalsReporting
You are selling, and the storefront is the smaller half of the problem
- Product type
- Commerce system
- Capability
- Commerce
- System
- CatalogueStockCheckoutPaymentsOrdersAdmin
There is a model that could help, and no safe place to put it yet
- Product type
- AI inside a process
- Capability
- AI
- System
- RetrievalGroundingConfidenceApprovalAudit
The same handful of tasks is done by hand, every day, by people who could be doing something else
- Product type
- Automation layer
- Capability
- Automation
- System
- TriggersConditionsApprovalsIntegrationsAudit
It works, and nobody can say which part of it is working
- Product type
- Measurement and extension
- Capability
- Data
- System
- EventsFunnelsCohortsReportsIntegrations
People need to find something, get in, and be counted at the door
- Product type
- Event technology
- Capability
- Product development
- System
- DiscoveryTicketingCheck-inAttendeesReporting
Nothing off the shelf fits, and the parts that do not fit are the parts that matter
- Product type
- Custom software
- Capability
- Custom software
- System
- Whatever the problem needsModelled firstThen built
Named by what they do rather than by which tool is used this year, because the tool is a decision made per project and the layer is not.
Interface
Frontend
The application people actually touch: state, routing, accessibility, performance, and motion that carries meaning rather than decorating.
This site
Mobile
A product that lives on a phone — offline behaviour, permissions, notifications, location, and the store release at the end of it.
System
Backend
The rules of the product expressed once, on the server, where they cannot be argued with by a client.
Database
The model everything else rests on. Getting this wrong is the only mistake that stays expensive for years.
Authentication
Accounts, sessions, roles and row-level permissions — including the external users who must see part of a system and no more.
Admin systems
The interface your team lives in. Built with the product rather than after it, because an unoperable system quietly becomes the developer's job forever.
Intelligence
AI
Retrieval over your own records, answers that cite their source, confidence thresholds, approval steps and an audit trail on every run.
Automation
Triggers, conditions and actions that a person in the business can change without opening a ticket with me.
Data and analytics
Events modelled at the start so questions asked later are queries, plus the dashboards and exports around them.
Connection
Payments
Checkout, payment states, refunds, commission and payouts — designed so the money is reconcilable at any moment, not just at the end.
Integrations
Mail, messaging, accounting, shipping, and internal systems with an endpoint — with the timeouts and duplicates handled, which is the part that matters.
Infrastructure
Environments, releases, domains, certificates, backups and monitoring — held in accounts that belong to you from the first day.
This site
Specific technologies are chosen per project and named in writing before anything is built — not listed on a website to look busy. This site is the exception, because you can check it: it is a Next.js and TypeScript application with no animation library, and the concept interfaces above are React components rather than images.
Tell me what you are trying to build and what is making it hard. If there is a fit I will say so quickly; if there is not, I will say that too.
- A reply
- Usually within two working days, from me.
- A conversation
- Scope, constraints, budget, timing. No pitch deck.
- A straight answer
- Including when I am the wrong person for it.