NewLife Services
Websites, Portals & Platforms
Websites, Client Portals & Internal Platforms
Most agencies build you a website. We build the website, the portal your clients log into, and the platform your team runs the company from — including the lead databases and automation running behind them.
Built, Not Templated
Public websites that convert, secure client portals with real role-based access, and the internal platforms businesses run their teams and their pipelines on. Designed and built in-house.
The problem
The Software Does Not Fit The Business
Most businesses are running a specific operation on software designed for the average of everyone — a template site that cannot do anything, five spreadsheets holding the real process, and a subscription for every function that none of the others can see.
None of that is a technology problem. It is a fit problem, and it is what this page is about.
What it is
Websites, Portals & Platforms, In Plain English
Three different products that get called the same thing. A website is public and the same for everybody. A portal is the part that only exists once somebody signs in, and it looks different for every person who logs into it. A platform is internal — the system your team actually runs the business from.
We design and build all three in-house, along with the lead databases and automation that run behind them.
Who it's for
Who This Works Best For
Businesses that have outgrown off-the-shelf software, or whose clients and partners need secure access to material that currently travels by email.
B2B Technology
Where the product is the system, and the internal tooling has to keep up with it.
See the B2B Technology playbook →Manufacturing & Industrial
Distributors, trade accounts and compliance documentation that cannot live in an inbox.
See the Manufacturing & Industrial playbook →Professional Services
Client reporting and document access that should not be a person manually sending files.
See the Professional Services playbook →Table of contents
What’s In This Guide
Twenty-three chapters across three tiers: the public website and what it has to be wired into, portals and the permission model behind them, and the internal platforms and lead databases a business is actually run from.
- 01Running On Somebody Else's Software
- 02Three Different Things
- 03The Three Tiers
- 04Tier One — What We Build
- 05Speed, Structure & Conversion
- 06Wired In From Day One
- 07Tier Two — What A Portal Actually Is
- 08One Login, Three Destinations
- 09The Part That Has To Be Right First Time
- 10What We Put Inside A Portal
- 11Tier Three — The System A Business Runs On
- 12We Built Ours First
- 13A Client HQ — Twelve Staff, Tracked Daily
- 14What An HQ Tracks
- 15Lead Database Centers
- 16Enrichment — What Makes It Actionable
- 17The Data Pipeline
- 18The Stack We Build On
- 19Who It Is For — And What We Talk People Out Of
- 20Scope To Launch
- 21What Is Included, And What It Costs To Run
- 22The Five Most Common Mistakes
- 23Proof — What We Have Built
The problem
Running On Somebody Else's Software
Most businesses are running a specific operation on software designed for somebody else's.
- The template site
- A good-looking page that cannot do anything — no booking, no login, no connection to the systems the business actually uses.
- The spreadsheet operation
- The real business runs in five spreadsheets, three chat threads and one person's head. It works until it does not, and it cannot be handed to anybody.
- The subscription pile
- A different tool for every function, none of them talking to each other, each charging monthly for a fraction of what is needed.
- Clients with nowhere to go
- Customers, investors or partners emailing for documents and updates that should live somewhere they can log into.
This is a fit problem, not a technology problem
Off-the-shelf software is built for the average of everyone. A business with any real specificity eventually outgrows it — and the symptom is never “our software is wrong”. It is five subscriptions, a spreadsheet nobody else can read, and a person who cannot go on holiday.
Nothing on this page is about replacing tools that work. It is about the gap between what your business actually does and what you can buy off a shelf.
Definitions
Three Different Things
Three products that get called the same thing, and cost very different amounts.
- Website
- For the public — anyone. Gets found, explains the business, and converts a stranger into an enquiry.
- Portal
- For people who log in — clients, investors, partners, staff. Gives a specific audience secure access to what belongs to them, and only that.
- Platform
- For your team, internally. The system the business is actually operated from — people, tasks, pipeline, data, reporting.
Why this distinction comes first
Almost every conversation about “a new website” turns out to be about one of the other two. Getting the tier right at the start is most of the value, because the three are scoped, priced and built completely differently.
The rest of this page goes tier by tier, so you can read only the part you need.
The map
The Three Tiers
Public, logged-in, internal. Everything below is one of these three.
Most agencies stop at the first tier. The other two are where the business actually runs — and they are the reason this page exists as something separate from a web design service.
Websites
Tier One — What We Build
The tier everyone understands — covered properly, but it is not what makes this page different.
- Custom design
- Designed for the business rather than selected from a theme. Brand, structure and layout decided against what the site has to achieve.
- Full build
- Every page built properly — service pages, location pages, case studies, blog architecture. Structure that SEO can actually work with.
- Content structure
- One page, one job. The architecture that makes a site rankable rather than a brochure with a menu attached.
- Ongoing development
- Sites are not finished at launch. New pages, new sections and new functionality get added as the business changes.
Websites
Speed, Structure & Conversion
Four build decisions that decide the results, all made before anything looks like anything.
- Speed is two things at once
- A ranking factor and a conversion factor. The same build decision affects both, which is why performance is not a polish step at the end.
- Mobile-first, genuinely
- Most traffic to most of our clients is mobile, so that is the layout designed first rather than adapted down afterwards.
- The conversion path
- Every page has a defined next action. A site that looks excellent and asks for nothing is a very expensive brochure.
- Built to be edited
- You should be able to change your own copy and images without a developer, and without breaking the layout.
Websites
Wired In From Day One
A website that is not connected to anything is just a poster.
- The CRM
- Every form, every booking and every enquiry lands in the pipeline with its source attached — not in an inbox.
- Tracking
- Analytics, pixels and conversion tracking installed and verified at build time, so the ads have data from launch rather than from month three.
- SEO
- Schema, metadata, sitemaps and indexing handled during the build, not retrofitted afterwards.
- Booking
- Calendars embedded and live, so somebody can book without a conversation first.
This is also the natural bridge into portals: once a site is connected to real systems, adding a login is a much smaller step than most businesses expect.
Portals
Tier Two — What A Portal Actually Is
The tier where this page starts covering ground most agencies do not.
A portal is the part of your website that only exists once somebody signs in. The public site is the same for everybody. A portal is different for every person who logs into it, because what it shows is determined by who they are.
Businesses ask for one when
- Clients keep emailing for documents, reports or updates
- Different audiences need different things from the same company
- Sensitive information cannot sit in email attachments
- The business wants to look like a serious operation
What it replaces
- A person manually sending files
- Separate systems, or one inbox doing everything
- Documents scattered across threads
- A contact form and a promise to get back to you
Case study
One Login, Three Destinations
Three audiences, three completely different portals, one place to sign in.
For a licensed producer client we designed and built a single sign-in on the public website that serves three entirely separate audiences. One login form. The system identifies who the person is and routes them to the portal built for them — with no visibility of the other two.
- Investor
- Shareholders and financial stakeholders. Performance reporting, financial documents and updates — the material that used to be emailed individually.
- Commercial
- Retail and trade accounts. Ordering, account information, trade and sell-sheet material.
- Licence & certification
- Regulatory and compliance access. Licensing documentation and certification records, kept separate and controlled.
What makes portal work genuinely hard
Not the interfaces. It is the single entry point, the role check behind it, and the guarantee that three audiences sharing one front door never see each other's material.
Investors, trade accounts and a regulator-facing compliance library are about as far apart as three audiences get — which is why this is the example we use rather than a friendlier one.
Portals
The Part That Has To Be Right First Time
Not the interesting part, and by some distance the most important one.
- Role-based access
- What somebody can see is determined by who they are, enforced on the server rather than hidden in the interface.
- Separation between audiences
- Different user groups can share a login page without ever sharing data.
- Account management
- Invitations, approvals, password resets, and revoking access when somebody leaves.
- Audit and visibility
- Knowing who accessed what — which matters enormously in regulated industries.
- Secure document handling
- Files served to authorised users only, rather than sitting behind a link somebody could guess.
We design the permission model before building the interface. Retrofitting access control is how security problems get created, and it is the single most common reason a portal cannot be trusted in production.
Everything visible in a portal is a permission decision. Get it wrong and a commercial account sees investor reporting. This is the least glamorous part of portal work and the part that most determines whether it can be used at all.
Portals
What We Put Inside A Portal
The common modules, though almost no two portals we have built contain the same set.
Document library
Controlled access to files — contracts, reports, certifications, trade material.
Reporting dashboards
Live performance data rather than a monthly PDF somebody has to compile.
Ordering & accounts
Trade customers placing orders and seeing their own history.
Messaging & requests
Structured communication that does not disappear into an inbox.
Onboarding flows
New users guided through setup rather than emailed instructions.
Notifications
People told when something relevant to them changes.
Modules are assembled per audience rather than shipped as a fixed product — an investor portal and a trade-ordering portal share almost nothing except the login.
Platforms
Tier Three — The System A Business Runs On
The tier almost no marketing agency offers, and the reason this page exists.
Not a project management subscription bent into shape
An HQ is a custom internal platform: one place where the whole operation is visible and the whole team works. Built around how a specific business actually operates, with the modules that business needs and none of the ones it does not.
The difference from a generic tool is not features. It is that nobody has to translate their actual job into somebody else's idea of a workflow.
Platforms
We Built Ours First
The strongest thing we can say about this tier is that we use it ourselves.
NewLife runs on its own HQ, every day. It tracks the team, what each person is working on, client revenue, cash position, active opportunities and goals. The whole team operates from it.
The argument we would make plainly: an agency that sells you an internal system and runs its own business on spreadsheets is selling something it does not believe in. We built ours first because we needed it — everything we have built for clients since came out of solving our own problem properly.
The dashboard at the top of this page is that system — not a mock-up of a product we are planning.
Platforms
A Client HQ — Twelve Staff, Tracked Daily
What the same idea looks like inside somebody else's business.
- Scale
- Twelve employees inside one system, each with their own role, responsibilities and visibility.
- Daily tracking
- What each person is doing, what has been completed, what is outstanding — visible to management without anybody being chased for an update.
- Leaderboard
- Performance across the team made visible rather than assumed.
- Live reporting
- Marketing performance, pipeline and revenue in the same place the team works, so nobody waits for a monthly report to know how the month is going.
- Briefings
- Work assigned into the platform weekly — who owns what, what is due, what is blocked.
Platforms
What An HQ Tracks
A list of modules is the least interesting way to describe this, so here is the only part that matters.
The modules are assembled per business, but the common set is: people and roles, daily task tracking, a performance leaderboard, live marketing and revenue reporting, sales pipeline, goal tracking against targets, and weekly briefings.
The point is not the feature list. It is that all of it lives in one place instead of six subscriptions that do not talk to each other — which is the actual problem most operations have.
Data platforms
Lead Database Centers
A lead engine that works while nobody is at a desk.
For B2B businesses we build custom lead database platforms — not a list you buy once, but a system that continuously sources companies matching your ideal customer profile and stores them in a structured database you own.
- Sourcing on a schedule
- Running continuously against your criteria from public company information, rather than a one-time list purchase that is stale within a quarter.
- A real database behind it
- Structured, deduplicated and queryable, so the data can be segmented and worked rather than sitting in a spreadsheet.
- Owned by you
- It is your database and your data, and it keeps growing whether or not anybody is running campaigns that week.
- Built to feed campaigns
- The output is an account list ready to be targeted, not a raw dump somebody has to clean first.
On sourcing: we scope what can be collected, from where, and under what terms as part of the build — data sourcing has legal and platform-terms considerations, and a B2B prospect's legal team is right to ask about them.
Data platforms
Enrichment — What Makes It Actionable
The layer between a list of company names and a campaign you can actually run.
A company name on its own is not actionable. Enrichment runs alongside the sourcing, layering in the detail that turns a company record into something you can actually target: contacts and roles inside the organisation, firmographic detail, and the attributes that decide whether an account is worth pursuing.
This is what makes account-based marketing possible at scale. ABM depends on knowing who the decision-makers are at named accounts — and that intelligence has to come from somewhere. For clients running it, this platform is the engine underneath.
Data platforms
The Data Pipeline
Four stages, continuously, whether or not anyone is looking at it.
Source, store, enrich, activate. The data pipeline runs on a schedule rather than when somebody remembers — which is the whole difference between a database that compounds and a spreadsheet that decays.
We say data pipeline in full on this page deliberately. On the CRM and ABM pages, “pipeline” means the sales pipeline. They are different things.
The stack
The Stack We Build On
Four layers, and one sentence about ownership that most software vendors avoid.
- Supabase
- The database layer behind our platforms — authentication, structured data, and the backend our lead centers and portals run on.
- Custom front-ends
- Interfaces built for the specific job rather than assembled from a template, which is what makes an HQ usable enough that a team actually opens it.
- Automation
- The scheduled processes — sourcing, enrichment, reporting refreshes — that run continuously in the background.
- GoHighLevel
- The CRM layer, connected so leads and pipeline move between systems rather than being re-entered by somebody.
Ownership, stated plainly
What we build is yours. The accounts, the data and the platform stay with you — which is not the norm in this category, and is worth asking every vendor you speak to.
Qualify yourself out
Who It Is For — And What We Talk People Out Of
The honest version, on the service where honesty is most expensive to skip.
This fits when
- Off-the-shelf nearly fits — But never quite does, and the workarounds have become the process.
- Different audiences need different access — To the same business, without seeing each other.
- The operation lives in spreadsheets — And in somebody's memory, which is a risk rather than a system.
- You are running ABM — And need the data engine behind it rather than a list you rebuy every quarter.
It is the wrong call when
- An existing tool genuinely does the job — We would tell you to keep it. This is the easiest service on the site to oversell.
- You need it live next week — Custom builds do not compress that far, and pretending otherwise is how projects fail.
- Nobody internally will own it — An unused platform is worse than no platform — it is the same problem plus a bill.
- The requirement is one form on one page — That is a website job, and a small one.
The “we would talk you out of it” framing matters more here than on any other page on this site, because custom software is the easiest thing we sell to oversell.
The process
Scope To Launch
Five phases, and the first one is where most of the value is decided.
- Scope
- We map how the business actually works before deciding what to build. Most of the value is decided here — building the wrong thing well is the expensive failure.
- Design
- Interface and permission model designed together. For anything with logins, who sees what is decided before a screen is built.
- Build
- Developed in stages, with working software to look at early, rather than a long silence followed by a reveal.
- Launch
- Data migrated, users onboarded, and the team actually trained on it. A platform nobody was shown how to use does not get used.
- Iterate
- It changes as the business changes. Platforms are not delivered and abandoned — ours are maintained and extended.
Why scope is the phase that decides the outcome
Every failed custom build we have been asked to rescue failed in the first two weeks, not the last two. The software was fine. It was built for a process the business did not actually follow.
The scope
What Is Included, And What It Costs To Run
What comes with a build, and the running costs most vendors leave until the invoice.
- Scope — mapping how the business actually works before anything is designed
- Custom design and full build, in-house, for the tier you are buying
- The permission model designed before the interface, for anything with a login
- CRM, analytics, conversion tracking, SEO structure and bookings wired in at build time
- Data migration, user onboarding and actual training for the team who will use it
- Hosting and infrastructure, stated up front rather than discovered later
- Maintenance, support and ongoing development as the business changes
- Ownership: the code, the data and the accounts stay with you
The honest part about ongoing cost
- Build
- Scoped and quoted per project, because a three-page site and a multi-role platform are not comparable work.
- Hosting and infrastructure
- Ongoing, and stated up front rather than discovered later.
- Maintenance and support
- Platforms need updating, and we would rather agree that now than have it lapse.
- Ongoing development
- Most clients keep extending what we have built, and that is the healthy outcome rather than an overrun.
Custom platforms carry running costs that a template site does not — hosting, the database, and the automation running continuously in the background. We put those numbers in the proposal rather than on this page, because they depend entirely on what gets built.
Read before you commission
The Five Most Common Mistakes
Every one of these turns up in builds we are asked to take over or replace.
- Mistake 01 — Building the interface before designing the permission model
- Which is how the wrong person ends up seeing the wrong data, and why retrofitting access control creates security problems rather than solving them.
- Mistake 02 — A beautiful website connected to nothing
- No CRM, no tracking, no bookings — so nothing can be measured and nothing can be followed up.
- Mistake 03 — Buying a lead list instead of building a lead engine
- A static list is stale within a quarter. A pipeline that keeps sourcing is not.
- Mistake 04 — Building a platform nobody is trained on
- The team quietly goes back to spreadsheets and the whole investment is wasted.
- Mistake 05 — Custom-building something an existing tool already does well
- We will tell you when that is the case, because it is the easiest way for this kind of work to waste your money.
Proof
Proof — What We Have Built
What is live, what runs on it, and what we are deliberately not claiming.
- Websites, live
- A&R Design Build, DMT Building Group, Sophia's Garden Artisan and Barrie Insulation Systems — all designed and built here, and all in the portfolio.
- A portal in production
- A single sign-in routing three separate audiences — investor, commercial, and licence and certification — with no visibility between them.
- Platforms in production
- Our own HQ, which the whole team runs on daily, and a client HQ operating with twelve staff inside it.
- What we will not claim
- A headline number we cannot source. This is the newest of our service lines to be written up, and the proof here is the work itself rather than a metric.
Straight answers
Websites, Portals & Platforms FAQ
What this costs to run, who owns it, how long it takes and what happens if we part ways — answered plainly.
What is the difference between a website, a portal and a platform?
A website is public and identical for everybody — it gets you found and turns a stranger into an enquiry. A portal is the part that only exists once somebody signs in, and it is different for every person who logs in because what it shows depends on who they are. A platform is internal: the system your team actually operates the business from. Most conversations that start with “we need a new website” turn out to be about one of the other two.
How long does a custom build take?
It depends entirely on the tier. A website is measured in weeks; a portal with real role-based access or an internal platform is measured in months, because the permission model and the data structure have to be designed before anything is built. What we will not do is quote a timeline that assumes scope we have not done yet — the scoping phase exists precisely so the estimate means something.
Who owns what you build — the code, the data, the accounts?
You do, all three. The platform, the database and the accounts stay with you. That is not the norm in this category, and it is worth asking every vendor you speak to, because the answer determines how much leverage they have over you later.
What does it cost to run once it is live?
Custom platforms carry running costs a template site does not: hosting, the database, and the automation running continuously in the background. We put those numbers in the proposal rather than on this page, because they depend entirely on what gets built — but they are stated up front rather than discovered on an invoice in month four.
Can you add a portal to the website I already have?
Usually yes, and it is a smaller step than most businesses expect once a site is already connected to real systems. What decides it is the existing build: whether it can carry authentication, and whether the data the portal needs to show already lives somewhere structured. We will tell you on the call rather than after a deposit.
Can different user types log in through the same place?
Yes — that is exactly what we built for a licensed producer client. One login form on the public site, then the system identifies who the person is and routes them to the portal built for them. Investors, trade accounts and compliance access all share one front door and never see each other's material.
Is our data secure, and who can see what?
Access is role-based and enforced on the server rather than hidden in the interface — which is the difference between a portal that is secure and one that merely looks it. Documents are served to authorised users rather than sitting behind a link somebody could guess, and access can be audited. We design the permission model before the interface, because retrofitting access control is how security problems get created.
What happens if we stop working with you?
You keep it. The code, the data and the accounts are yours, so the platform keeps running and another developer can pick it up. We would rather you stay because the work is good than because leaving is painful.
Can you connect it to the tools we already use?
Usually, and we would rather connect than replace. If an existing tool genuinely does its job well, the right build is the one that talks to it instead of duplicating it — the CRM layer in particular is normally a connection rather than a rebuild.
Do you build the lead sourcing, or is that a third-party tool?
We build it. The sourcing, the database behind it and the enrichment layer are all part of the platform rather than a subscription you rent — which is why the database is yours and keeps growing whether or not a campaign is running. We scope what can be collected and under what terms as part of the build.
How is an HQ different from a project management app?
A project management app asks your business to describe itself in somebody else's vocabulary. An HQ is built around how your operation actually works, with the modules you need and none of the ones you do not — people, tasks, leaderboard, live reporting, pipeline and briefings in one place rather than six subscriptions that do not talk to each other. The test is simple: does the team open it without being told to?
Why NewLife
You, In-House, Or A Typical Agency
Everything we do runs on one system we call The Film-to-Funnel System — in-house film → paid ads → landing page → CRM follow-up → optimize. Here's how that stacks up against doing it yourself or hiring a typical agency.
| In-house | Typical agency | NewLife | |
|---|---|---|---|
| Creative | You film it on a phone | Outsourced or stock footage | Our in-house cinema crew, filmed on-site |
| Who does the work | You, between running the business | A junior account manager | Cruz and the senior team, directly |
| The system | Disconnected tools that don't talk | Ads, then hands-off | Film → ads → landing page → CRM, one connected system |
| Your accounts & data | Yours — but no time to run them | Often held hostage | Always yours — you keep everything |
| Follow-up | Manual, when you remember | Rarely their problem | Automated speed-to-lead in the CRM |
| Local knowledge | You know your market | A national, generic playbook | Barrie & Simcoe County, on the ground |
Keep building
Services That Work Together
Meta Ads
$736K reported value on $6.05K spend
Explore Meta Ads →Google Ads
$751.7K reported value on $11.07K spend
Explore Google Ads →LinkedIn Ads
Named accounts, the whole buying committee
Explore LinkedIn Ads →SEO
Page 6 → #3 on page 1 in 35 days (DMT Building Group)
Explore SEO →Social Media Marketing
7 reels + 20 carousels a month for one client (Chicken On The Run)
Explore Social Media Marketing →Creative Production
Cinema shoots on location — Aruba, Thunder Bay, Tampa & DC
Explore Creative Production →CRM Systems
$280K in new pipeline value in 30 days (DMT Building Group)
Explore CRM Systems →Software Solutions
3 platforms, one login — CRM, SEO & social, run for you
Explore Software Solutions →Account-Based Marketing
Land and expand larger B2B deals with a named-account approach
Explore Account-Based Marketing →Go-To-Market Strategy
A costed route to market — ICP, positioning, channels and the first 90 days
Explore Go-To-Market Strategy →Demand Generation
Create demand, don't just harvest it
Explore Demand Generation →Intent & Signal Marketing
Reach accounts while they are looking
Explore Intent & Signal Marketing →Last step
Book Your Free Platform Strategy Call
One call. We look at your market, your numbers and your goals, and you leave with a written growth plan — yours to keep whether we work together or not. You'll talk to Cruz or Keegan directly — never a sales rep.