What kinds of projects fit Pernito?
Websites, search and content work, dashboards, useful software, and systems that connect them. If your idea crosses a few of those areas, that is usually a good starting point for a conversation.
Questions worth asking
Straight answers about the kind of work that fits, how projects start, what happens after launch, and what to expect if you write. The answers here are the same ones I give in person.
- Short answers
- No hedging, and no sales language
- Missing something
- Ask it directly
- Still unclear
- A short conversation fixes most of it
- Next step
- Email or use the brief helper
Getting started
Do I need a detailed brief?
No. A clear description of what feels stuck, what you hope to change, or what you wish existed is enough to begin. The shape of the project can be worked out together.
Can you help with an existing site or tool?
Yes. An existing project can be reviewed and improved without starting over. The first step is understanding what already works and where people are getting held up.
How does the work usually start?
With a short conversation about the problem, followed by a written summary of what I understand, the shape of the work, and what I would do first. You read it, change what is wrong, and decide from there.
What if I am not sure which service fits?
Describe the problem instead of the solution. The first conversation is about working out what is really in the way, which usually points to the right area quickly.
How much does a project cost?
This site does not publish prices, packages, or rates, because a number without the scope behind it is misleading. Once the work is understood, you get a written estimate you can compare against other options.
The work itself
Can I hire you for just one area of work?
Yes. Many projects begin with one area and grow. If the work needs the others later, that can be handled as a separate piece of work rather than hidden inside the first one.
Do you work with existing teams or agencies?
Often, yes. Working alongside an in-house team or another studio is normal, and clear ownership of decisions matters more than who does the typing.
Do you design and build, or only one of them?
Both. Working on the whole experience means the structure, the words, the look, and the behaviour are designed together instead of negotiated between separate specialists.
What platforms do you build on?
Static sites where they fit, and a content-managed build where the site genuinely needs one. The choice follows from how the site will be maintained, not from a preference for a tool.
Will my site be accessible and fast enough?
Accessibility and speed are part of the build rather than an extra phase. Semantic markup, keyboard support, contrast, and image weight are handled while the site is being made, and checked before launch.
Can you work on a site that already exists?
Yes. Sometimes the right work is a focused improvement to a small number of pages rather than a rebuild, and sometimes it is a rebuild. The starting point is understanding what the current site is doing well and where it gets in the way.
Can you guarantee first place in search?
No, and anyone who promises it is guessing. What I can do is build the foundations, write content that answers real questions, and give you honest measurement so you know what is improving and what is not.
What does AI answer readiness mean?
It means a page is structured so an assistant can read it reliably: a clear heading, a direct answer near the top, consistent facts, and structured data that describes the page. The result is that your content is easier to quote accurately.
Do you write the content or do I?
It depends on your situation. I can draft from interviews and notes, write from an outline you approve, or edit and structure content your team produces. The part that always stays the same is accuracy.
How do you measure whether search work is working?
With a small set of measures tied to decisions: impressions and clicks for the pages that matter, what people do next, and how fast content is found. Traffic totals are useful, but they are not the point.
Practical details
Do you work with the tools we already use?
Usually yes. A dashboard often sits on top of a spreadsheet, a database, a form, or a platform you already pay for. The work is usually about making those sources legible in one place rather than replacing them.
How do you decide what a dashboard should show?
By starting from the decision. I want to know what someone does differently depending on what they see. Anything that does not change a decision is a candidate for leaving out, however interesting it looks.
Can a tool handle permissions and private data?
Yes, and that is part of the design rather than an add-on. Access is scoped to what each person needs, and the interface never displays data a viewer is not allowed to see, including in exports and caches.
What happens after a tool is built?
You get documentation, a walkthrough, and a way to keep the tool healthy. That usually means a short handover, a simple way to report an issue, and a plan for what to review when the underlying data changes.
Where should AI be used in a workflow?
On the steps where a person currently retypes, reformats, or summarises the same kind of thing, and where being slightly wrong is easy to spot. I keep AI away from decisions that carry legal, financial, or reputational weight unless a person reviews them.
What happens when an automated step fails?
It stops and says so. Failures are reported to the people who can fix them, with enough context to understand what happened, and a retry that is safe to run. Nothing carries on quietly with bad data.
Will this lock us into a platform?
I aim not to. Workflows are described in ordinary language, the data flows through documented steps, and where a platform does the work, the alternative is written down. Leaving should be a decision, not an extraction.
How much of a workflow can run without you?
After handover, the workflows run on their own and you maintain them. I document how each one behaves, what it depends on, and what to check when something changes upstream.
How long does a project take?
It depends on the scope, and I would rather give you a range than a date I cannot keep. After the first conversation I write down what I think the work involves, so you can see the shape of it before anything is agreed.
Do you work in stages or all at once?
In stages, but they are not fixed. Each stage ends with something you can look at and react to, and what I learn from your reaction changes what happens next.
What if I do not like the direction?
That is useful information rather than a problem. Early in the work, changing direction is cheap. The point of showing you work before it is finished is so corrections happen while they are still cheap to make.
Do you work with clients in other countries?
Yes. The practice works online, with written summaries and recorded walkthroughs so nothing depends on being in the same room. Time-zone differences are handled by agreeing on response windows rather than by working around them constantly.
Is support available after launch?
Support after launch is arranged as needed rather than sold as a default package. If you would rather not have that conversation now, that is fine, and the handover notes are written so the work can be maintained without me.
About the practice
Is Pernito a one-person practice?
Yes. Josh handles strategy, design, build, and handover directly, with other specialists brought in for specific parts of a project when they are genuinely needed.
Where is the practice based?
The practice works online rather than from a fixed office, which means it works with people in different places and time zones. Written summaries and recorded walkthroughs keep that working well.
Why does the site not show case studies or results?
Because invented examples and unverified numbers are worse than none. The site describes the work honestly instead of borrowing credibility it has not earned, and real examples get added when there is something genuine to show.
Can I see how this site is built?
Yes. The site is plain HTML, CSS, and a small amount of JavaScript, hosted on Cloudflare Pages, and its source is in a public repository. There is no framework behind it and no third-party script running on the page.
What happens when I send a message?
The message arrives in Josh’s inbox as an ordinary email, and the next step is a reply that either answers the question or suggests a short conversation to work out the shape of the project.
What should I include in a first message?
What you are trying to do, what is getting in the way, and when it matters. If you would rather talk than write, say so and suggest a couple of times that work.
Does this site store my message?
No. The brief helper builds a draft in your own mail app and sends nothing by itself. Nothing you type is stored by this site, and no database or third-party form service is involved.
Question not answered here?
Ask it directly. If it is a good question, it probably belongs on this page too.