Apps & Features
Apps and features your team will actually use.
Client portals, internal tools, and new features for an app you already have: scoped tightly, built by us or with imme, and measured after launch.
Where app projects go wrong
They start from a feature list instead of a job to be done. Scope grows, launch slips, and six months later the team still keeps the spreadsheet open next to the shiny new tool, because the spreadsheet does the one thing they needed.
We start from the job the tool has to do, build the smallest version that does it well, and measure whether people use it. Then we add what the usage tells us to add.
What we build
- Client portals: logins, documents, requests and status updates your clients can check without emailing you.
- Internal tools: CRMs, call queues, intake forms and dashboards built around how your team already works.
- New features for an existing web app: scoped, built and shipped without a rewrite.
- Connections between tools: website forms into your CRM, email inside the client record, payments recorded where your team looks for them.
Who does what
We build some apps ourselves. On others, imme designs and builds alongside us. Scoping, the flows, the words on screen, the tracking and the point of contact are always ours.
| Part of the project | Who |
|---|---|
| Discovery and scoping: what it must do, and what it can skip | Noble Harbor |
| Feature plan and user flows | Noble Harbor |
| Copy and in-app content | Noble Harbor |
| Analytics and event tracking | Noble Harbor |
| Launch checklist and the first 30 days after launch | Noble Harbor |
| Your day-to-day contact | Noble Harbor |
| The build | Noble Harbor, or imme with Noble Harbor. Each proposal names who builds. |
An example: the portal behind this site
Noble Harbor runs on a private portal we built ourselves. A message from the contact form lands in it as a lead. A call queue puts follow-ups in order. A phone photo of a business card becomes a lead record, and Gmail threads show up inside the lead they belong to. It's the same kind of tool we build for clients: small, specific, and used every day.
How a project runs
- A free 30-minute consult: the job the tool has to do, and whether we're the right fit.
- A written proposal: scope, who builds, price and timeline, before any work starts.
- Scoping and user flows, agreed with the people who will use it.
- Build in small releases you can try as we go.
- Launch, with tracking in place.
- The first 30 days: watching real use, and fixing what gets in the way.
Pricing
Apps and features are quoted per project after the free consult. The proposal sets out the scope, who builds and the price before anything starts. If the tool needs content or SEO around it, that can sit inside a monthly retainer: see pricing.
Pairs well with
A new tool often comes with a new or rebuilt site: see websites. When the point of the tool is better numbers, customer analytics makes sure you can see them.
Recent work
Built by Noble Harbor
Noble Harbor Marketing website and client portal
Noble Harbor Marketing · Hilton Head Island
The site you're on, and the private portal behind it: a CRM with leads, a call queue, business-card capture from a phone photo, and Gmail built into each lead.
Website · App · Content & SEO
Frequently asked questions
Do you build mobile apps?
We build web apps that work on phones, tablets and computers from one codebase, with no app store in between. If you need an app in the App Store or Google Play, raise it on the consult and we'll tell you plainly whether we're the right team for it.
Who actually builds it?
Either Noble Harbor, or imme, our design and build partner, working with us. Each proposal names who builds. Either way, we scope it, plan the flows, write what's on screen, set up the tracking, and stay your contact.
How much does it cost?
It's quoted per project after a free 30-minute consult, because a client login with a document library and a custom CRM are very different jobs. The proposal states scope and price before any work starts.
Can you add a feature to an app someone else built?
Often, yes. We start by reading the code and how it's set up, then tell you what the feature takes, or whether it's cheaper to rebuild that part. You get that answer before you pay for the build.
What happens after launch?
For the first 30 days we watch whether people use it and fix what gets in their way. Ongoing changes and support can be quoted with the project, so you know the cost of keeping it running.
Do you meet in person?
On Hilton Head and in Bluffton, yes. Savannah and Charleston clients meet us by video, or in person by arrangement. Everyone else works with us by video.
Start with a conversation
Tell us what the tool has to do.
Thirty minutes, free. We'll talk through the job, what already exists, and the smallest version worth building.