Supporting the daily reality of education technology.
I work with devices, accounts, classroom tools, support requests, and troubleshooting. The job is helping people get back to their work with less confusion and a clearer next step.
School IT / web systems / practical AI / clearer paths
I make technology feel calmer, clearer, and easier to trust.
I'm Francisco Gramajo, an IT support professional, web systems builder, and founder of OK to Great Web Studio.
My work sits between people and technology: fixing what breaks, simplifying what feels confusing, documenting what matters, and building better paths so tools feel less like obstacles and more like quiet support.
Technology feels best when it becomes almost invisible because it just works.
From Okay → GREAT — because every system, process, and person has upgrade potential.
Now
What I'm focused on now.
Right now, most of my attention goes toward supporting school technology, building clearer web systems, and using AI carefully to make planning and documentation less painful.
Making websites easier to understand and maintain.
I care about websites that load quickly, guide visitors clearly, and avoid turning every update into a small negotiation with the codebase.
Using AI where it sharpens the work.
I use AI for planning, drafting, summarizing, QA, study support, and turning rough information into usable structure while people keep judgment.
Turning solved problems into reusable context.
Good documentation keeps people from solving the same problem from scratch and helps the next person continue without guessing.
How I work
The principles I come back to.
When a support request, website, workflow, or tool starts getting messy, these are the defaults I return to.
Start with the real user moment.
Before fixing the tool, understand what the person was trying to do, where the system failed them, and what would make the next attempt easier.
Prefer clarity over cleverness.
A plain label, reliable checklist, or obvious path beats a clever system people avoid. Cleverness gets expensive when it creates interpretation work.
Document the handoff.
Useful notes preserve the decision, the context, the current state, and the next likely question. If the next person cannot understand what changed, the work is not finished.
Ship the useful version.
Polish matters, but usefulness comes first. A smaller working version with clear constraints usually beats a perfect plan that never reaches the person who needs it.