PipelineDealUnderwritingMarketAI analysisIC memo
CREUW AI
A commercial real estate platform that follows one deal from first look to investment committee.
Web Development: Systems that carry real business.
Applications and platforms designed around how your business actually runs, then engineered so the tenth feature is as easy to ship as the first.
What are you building?
The name on the brief says little. The parts it is made of say almost everything about cost, risk and time.
SaaS platform: One product, many customers, each seeing only their own world.
Marketplace: Two kinds of people who need to find, and trust, each other.
Dashboard: Scattered numbers, brought into one view a team can act on.
Customer portal: A signed-in place where customers help themselves.
E-commerce: A catalogue, a checkout and everything that happens after the order.
Internal platform: The tool that replaces the spreadsheet everyone is afraid to touch.
Modernisation: A working product, moved onto foundations that will hold.
- What makes it hard
- Tenancy, plans and permissions touch every table and every screen. Adding them later is close to a rewrite.
- What we settle first
- How customers, plans and roles are modelled, before the first screen is drawn.
- What makes it hard
- Two audiences with opposite needs, and money moving between them. Search quality decides whether the place feels alive.
- What we settle first
- Which side to serve first, and how payment, fees and disputes work.
- What makes it hard
- The data arrives late, duplicated and in five formats. The chart is the easy part.
- What we settle first
- Which decisions the dashboard has to support, and which sources can be trusted.
- What makes it hard
- It has to agree, at every moment, with the systems your staff already use.
- What we settle first
- What the system of record is, and what the portal is allowed to change.
- What makes it hard
- Speed on a phone, stock that is never wrong, and a checkout with nothing in the way.
- What we settle first
- Platform, custom, or both. It depends on how unusual the way you sell is.
- What makes it hard
- The real process lives in people's heads, and in exceptions nobody wrote down.
- What we settle first
- Time with the people who do the work, before deciding what to build.
- What makes it hard
- The business cannot stop while the engine is replaced.
- What we settle first
- What is actually limiting you. Usually a few parts, rarely all of it.
What web development means here
Web development at SOLOGEN means designing and engineering software that runs in the browser: customer-facing applications, SaaS platforms, dashboards, marketplaces, portals and the internal systems that connect them.
Who usually needs it
- A founder turning a validated idea into a first release
- A business replacing spreadsheets and email with one system
- A product team whose MVP is slowing down under real usage
- An operation that needs its existing systems to talk to each other
How far it needs to go.
Web products sit on a staircase. Each step up includes everything below it, and we build at every level.
A site that has to perform
Fast on a phone, easy for your team to update, structured so search engines and people both find what they came for.
An application with accounts
People log in and do their work in it. Permissions, data that must stay correct, and screens for the awkward cases as well as the happy path.
A platform with money in it
Subscriptions, payment providers, the systems you already run and the background work that keeps them all in step.
A system at scale
Many customers, heavy data, several teams shipping at once. Architecture, monitoring and release practices carry as much weight as features.
Four habits we do not skip.
Architecture before code.
How data, services and interfaces fit together is decided first, and written down. It is why the tenth feature costs about what the first did.
Performance is designed, not tuned.
What renders on the server, what loads later and what never reaches the browser at all are choices made at the start, when they are cheap.
Designers and engineers, same room.
The people drawing the interface and the people building it work on the same product at the same time, so what is designed is what ships.
Built to be handed over.
Readable code, documentation and a clear deployment path. Your product should never depend on one person's memory, including ours.
What we build it with.
Proven tools, chosen for the product and the team that will own it. Open a layer to see why each choice matters.
Frontend
Everything people see and touch in the browser.
The frontend decides how fast a product feels and how easily search engines can read it. The right choice keeps pages quick as features are added.
- React
- Component-based interfaces that stay maintainable as a product grows.
- Next.js
- Server-rendered React for products that need to be fast and searchable.
- TypeScript
- Typed code that catches mistakes before your users can.
Backend
The logic, APIs and integrations behind the interface.
The backend carries your business rules. A well-structured one makes new features cheap and keeps the product stable when usage climbs.
- Node.js
- Fast, event-driven services and APIs that share a language with the frontend.
- NestJS
- Structured, testable Node.js architecture for larger systems and teams.
- .NET
- Enterprise-grade services, especially where they meet existing Microsoft systems.
Databases
Where your product's information lives and stays correct.
Data outlives code. The right model keeps information consistent, queries fast and future reporting possible.
- PostgreSQL
- A dependable relational default for structured data and complex queries.
- MySQL
- Proven relational storage, often the right fit alongside existing systems.
- MongoDB
- Flexible document storage for data whose shape changes often.
Cloud & Infrastructure
Where the product runs, scales and recovers.
Infrastructure decides reliability and running cost. We fit the platform to your scale, your team and any systems you already use.
- AWS
- Broad, mature infrastructure for products that need room to scale.
- Azure
- A natural fit for organisations already built around Microsoft.
- GCP
- Strong data and machine-learning services alongside general infrastructure.
- Firebase
- Managed backend services that get mobile and real-time products live quickly.
- Supabase
- A managed PostgreSQL backend with authentication and storage built in.
And after launch?
The same team stays on. Launch is where the most useful information starts arriving.
Watch
Monitoring and alerts are live before the launch is. We stay close while real traffic finds what testing could not.
Fix
Real users do unexpected things. Those findings are triaged against the goals you set at the start, and the important ones are shipped quickly.
Extend
A regular rhythm of review and release. The roadmap is rewritten from what the product has taught you.
Before you ask.
What kinds of web products do you build?
Custom web applications, SaaS platforms, dashboards, marketplaces, customer portals, e-commerce and internal business systems. Most products turn out to be two or three of these at once, which is why we start from the business problem instead of a product category.
Can you design the product as well as build it?
Yes. Product design is one of our five disciplines, and designers work alongside the engineers building your product. You can also bring existing designs and we will build from those.
We already have a product. Can you take it over or modernise it?
Yes. We begin by reading the code and the data model, then propose changes in steps your team can release one at a time. A full rewrite is a last resort, and we will tell you when it is not needed.
Which technologies do you use for web development?
Most often React and Next.js with TypeScript on the frontend, Node.js, NestJS or .NET on the backend, PostgreSQL for data, and AWS, Azure or GCP for infrastructure. The choice follows the product and the team that will own it.
What happens after launch?
The same team stays on. We monitor the product, fix what real usage reveals, and plan the next release with you. Launch is where the most useful information starts arriving.
How do we get started?
Tell us what you are building in the project brief. It takes a few minutes and gives us enough to come back with the right people and the right questions.
