Add portfolio content and design spec for Otis
This commit is contained in:
48
content/services.md
Normal file
48
content/services.md
Normal file
@@ -0,0 +1,48 @@
|
||||
# Services
|
||||
|
||||
## Workflow Automation
|
||||
I build automated pipelines that replace repetitive manual work. From form submissions to multi-step approval flows, I connect your existing tools (Google Workspace, email, chat, notifications) into workflows that run themselves.
|
||||
|
||||
**What this looks like:**
|
||||
- Multi-step approval workflows with email and push notifications
|
||||
- Scheduled reports and notifications across multiple channels
|
||||
- Data sync between internal systems
|
||||
- Form-based intake that triggers automated processing
|
||||
|
||||
**Tools:** n8n, Node.js, REST APIs, Google Workspace APIs, Webhooks
|
||||
|
||||
---
|
||||
|
||||
## AI-Powered Internal Tools
|
||||
I integrate LLMs into practical business tools — not chatbots, but agents that do real work. Natural language interfaces for scheduling, document drafting, and data processing.
|
||||
|
||||
**What this looks like:**
|
||||
- AI agent that reads calendars, drafts emails, and plans schedules from plain-text requests
|
||||
- Document classification and routing
|
||||
- Smart data extraction from unstructured inputs
|
||||
|
||||
**Tools:** OpenAI, Anthropic, DeepSeek, LangChain, tool-calling agents
|
||||
|
||||
---
|
||||
|
||||
## Document Processing
|
||||
I build services that handle PDF and Word document manipulation at scale. Template-based generation, splitting, merging, metadata extraction — exposed as APIs your other systems can call.
|
||||
|
||||
**What this looks like:**
|
||||
- DOCX generation from templates (contracts, letters, forms)
|
||||
- PDF splitting and renaming based on content
|
||||
- Batch document processing pipelines
|
||||
|
||||
**Tools:** Node.js, pdf-lib, docxtemplater, Express, REST APIs
|
||||
|
||||
---
|
||||
|
||||
## Custom Web Applications
|
||||
I build focused web apps that solve specific operational problems. Clean UI, fast, deployed and ready to use.
|
||||
|
||||
**What this looks like:**
|
||||
- Employee-facing internal tools
|
||||
- Data validation and reporting dashboards
|
||||
- Absence and scheduling systems
|
||||
|
||||
**Tools:** Next.js, React, TypeScript, Tailwind CSS
|
||||
Reference in New Issue
Block a user